Recommended Free Tools
The best web banner campaigns start with the placement, not the artwork. Use the current IAB New Ad Portfolio as a baseline, confirm the destination publisher’s exact requirements, keep the creative light and non-intrusive, place disclosures beside the claims they qualify, and measure viewable impressions separately from served impressions. This workflow helps advertisers, designers, publishers and small businesses produce banners that render reliably without promising performance that the available evidence cannot guarantee.
1. Start with the current placement requirements
Banner specifications are not universal. The IAB Tech Lab’s New Ad Portfolio: Advertising Creative Guidelines, updated February 7, 2024, moved display guidance toward flexible units defined by aspect ratios and size ranges rather than a short list of fixed desktop and mobile pixels. That makes a creative more adaptable to responsive layouts, but it does not override a publisher’s upload rules.
Build a placement brief
- Record the publisher, section, device environments and dates.
- Copy the accepted file formats, maximum file size, minimum pixel dimensions, animation limits, click-through method and tracking requirements.
- Note whether the placement is responsive, fixed, in-feed, interstitial, sticky or embedded inside an app.
- Confirm whether the publisher requires separate desktop, mobile, retina or dark-mode assets.
Apple News illustrates why this check matters: its documented banner rules include accepted image formats, minimum dimensions, file-size ceilings and an animation limit of no more than three GIF loops and 15 seconds total. Those are Apple News requirements, not a general web standard. Reconfirm specifications immediately before trafficking because platforms can change them.
Choose a responsive range instead of one “standard” size
When a publisher supports IAB flexible units, design around the supplied aspect-ratio range and test the minimum and maximum containers. Keep the logo, offer, qualification and call to action inside a protected area that remains readable at the smallest supported width. If the publisher still requests fixed dimensions, deliver those dimensions exactly and ask whether additional responsive variants are accepted.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →2. Design for respect, control and choice
The IAB portfolio’s experience principles are Respect, Control and Choice. A reader’s primary task is consuming the publisher’s content; the ad should not obstruct that task or make it difficult to understand what is happening.
Make the message understandable at a glance
- Use one primary promise and one clear action. A banner that tries to explain every feature becomes unreadable at narrow widths.
- Use a strong contrast between text and background, and maintain a visible focus or hover state for interactive elements.
- Do not make the entire banner an ambiguous click target if the user cannot tell where it leads.
- Keep branding visible so the reader can identify the advertiser before clicking.
Avoid disruptive behavior
- Do not cover editorial text, trap scrolling, or force sound on.
- Do not add unnecessary expansion, flashing, rapid motion or deceptive close controls.
- Respect the publisher’s frequency, size and interaction rules.
- Provide a usable experience on touch screens, keyboard navigation and slower connections where the format supports interaction.
Lightweight, encrypted and AdChoices-supported experiences are emphasized by the IAB portfolio. Follow the destination publisher’s privacy and consent implementation rather than adding an independent mechanism that conflicts with it.
3. Treat an HTML5 banner as a small web project
An HTML5 creative can contain HTML, CSS, JavaScript, SVG and media. The way those assets are packaged affects how quickly the first useful frame appears, and the complete package—not just the source file—must be tested in the ad-operations workflow.
#1 Best Overall
Keep the first render small
- Compress raster images and use the format the publisher accepts.
- Remove unused fonts, libraries, images and code.
- Prefer vector artwork for simple logos and shapes, but verify that the ad server supports the SVG implementation.
- Defer nonessential animation and interaction until the core message is visible.
- Set explicit image dimensions to reduce layout movement.
- Use short, self-contained scripts and avoid requests to domains the publisher has not approved.
Package and test the complete creative
- Export the final HTML, styles, scripts, images and tracking assets into the package structure required by the publisher.
- Open the packaged creative in the publisher’s preview or validator, not only in a local browser.
- Test first paint, click behavior, fallback artwork, animation end state and destination URL.
- Check desktop, mobile, high-density displays, zoomed text, slow connections and any required dark-mode variant.
- Send the exact package and tracking instructions to ad operations before the campaign is scheduled.
4. Write claims and disclosures that survive every screen
For U.S. campaigns, the Federal Trade Commission says disclosures needed to prevent deception must be “clear and conspicuous.” Put a qualification next to the claim it changes, use plain language, and make it legible in every supported placement.
Common claim problems
- A “free” headline with the recurring charge or eligibility condition hidden in tiny type.
- A percentage discount that does not state the required purchase or expiration where the reader sees the offer.
- A “results” statement that implies typical performance without the information needed to interpret it.
- A disclosure placed below the visible crop or inside a hover state that does not exist on touch devices.
The FTC’s device and platform guidance means a disclosure that works on a large monitor may fail on a phone. Check contrast, minimum type size, line wrapping and animation timing in the smallest supported container. If the qualification is essential, reserve design space for it instead of trying to add it after the artwork is complete. Legal requirements differ outside the United States, so obtain local advice for other jurisdictions.
5. Build measurement around viewability
A served impression only shows that an ad was delivered. It does not establish that a person had an opportunity to see it. Google Ad Manager’s summary of the IAB display criterion defines a standard display ad as viewable when at least 50% of its pixels are visible for one continuous second. For ads larger than 242,000 pixels, the threshold is 30% of pixels.
Separate the reporting fields
| Metric | What it tells you | What it does not prove |
|---|---|---|
| Served impression | The ad was delivered by the serving system. | That it was in the viewport or noticed. |
| Viewable impression | The measured pixel-and-time criterion was met. | That the reader read, understood or clicked it. |
| Click | The tracking system recorded an interaction. | That the landing page loaded or produced a sale. |
Review viewable impressions alongside placement, device, page position and screen context. A high served count with weak viewability may indicate that inventory is below the fold, inside a rapidly scrolled area or affected by layout changes. Do not convert these criteria into a guaranteed click-through or conversion rate; no such outcome is established by the cited guidance.
6. A production checklist before launch
Creative and accessibility
- The main offer, brand and action are identifiable without sound.
- Text remains readable at the smallest approved size and on high-density screens.
- Contrast, focus states and alternative or fallback artwork have been checked.
- Motion ends in a stable frame and does not interfere with reading.
Technical delivery
- Every file is within the publisher’s current size and format limits.
- All paths work inside the packaged creative; there are no accidental local references.
- Click tracking, redirects, custom parameters and privacy requirements match the ad-operations instructions.
- The creative has been tested in the publisher’s validator and preview environment.
Claims and reporting
- Required qualifications sit beside the relevant claim.
- U.S. disclosures are clear and conspicuous on each supported device.
- Served and viewable impressions are reported as separate measures.
- Stakeholders know which publisher and placement rules govern the delivery.
7. Troubleshooting common banner failures
The ad is rejected for size or format
Cause: You used a generic specification or an outdated publisher sheet. Fix: Reopen the current placement brief, export the exact accepted format and dimensions, and remove unapproved animation or files.
The first frame is blank or arrives late
Cause: Large images, fonts or scripts block initial rendering. Fix: compress assets, remove unused dependencies, set dimensions, show the core message first and defer optional work.
The click does not register
Cause: An overlay, incorrect click variable or redirect rule prevents the ad server from receiving the event. Fix: test the packaged creative in the publisher’s preview, verify the click-through implementation and provide the exact tracking instructions to ad operations.
The disclosure disappears on mobile
Cause: It is outside the crop, too small, low contrast or hidden in an interaction unavailable on touch screens. Fix: reserve layout space, increase legibility and test the smallest supported viewport.
Served impressions are high but viewability is low
Cause: The placement is frequently outside the viewport or the page changes before the one-second criterion is met. Fix: compare results by placement and screen context, then discuss inventory position or creative loading with the publisher.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsRank #4
8. Or skip the browser setup
If you need screenshots of landing pages, creative previews or campaign destinations for QA, ScreenshotNeo returns a clean PNG, JPEG, WebP or PDF from one request. It accepts cookie and consent banners before capture and removes more than 60 known consent platforms, newsletter popups and chat widgets; each step can be disabled. Bot checks, CAPTCHAs, blank pages, timeouts, failed loads and cache hits are not billed, and response headers identify the page verdict and whether the request was billed.
Use the API documentation at https://screenshotneo.com/docs/. Replace the URL with your own preview or landing page:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
For banner QA, options include full-page capture with lazy images loaded, a CSS-selected element, custom viewport or device, retina scale, dark mode, custom CSS and JavaScript, clicks before capture, hidden selectors, waits for a selector, delay or network idle, blocked ads or resource types, custom headers and cookies, timezone and geolocation, transparent backgrounds, resizing, chosen cache TTL, signed image links, asynchronous jobs with signed webhooks and bulk capture of up to 100 URLs per call. An MCP server provides take_screenshot, get_page_info and capture_pdf tools for Claude, Cursor and other MCP clients.
The Free plan includes 1,000 screenshots each month with no card. Paid plans start at $5 for 3,000 shots; every feature is included on every plan, and yearly billing gives two months free. Create a free ScreenshotNeo account to begin.
9. Choosing between implementation options
| Option | Best fit | Primary trade-off |
|---|---|---|
| Static image | Simple offers, strict file limits and broad compatibility. | Less interaction and no adaptive behavior beyond supplied variants. |
| HTML5 banner | Responsive layouts, animation or controlled interaction. | More packaging, testing and ad-operations coordination. |
| Publisher-hosted responsive unit | Placements that define their own flexible container. | Less control over the final rendering; publisher rules govern. |
Compare each option on responsive range, initial-load work, user disruption, claim legibility, viewability reporting and acceptance requirements. Choose the simplest implementation that meets the placement and measurement needs.
Best Value
Frequently Asked Questions
Are fixed 300×250 or 728×90 banners still universal standards?
No. The IAB New Ad Portfolio uses flexible units, and each publisher can impose its own dimensions, formats and limits. Treat familiar pixel sizes as placement-specific requirements, not universal rules.
Does a viewable impression mean someone saw or understood the ad?
No. It means the measured pixel-and-time threshold was met. Attention, comprehension and conversion require separate analysis.
Do FTC disclosure rules apply outside the United States?
The cited FTC guidance is U.S.-specific. Other jurisdictions may impose different requirements, so obtain local legal advice for campaigns shown elsewhere.
Free tools Windows power users keep installed
One-click scans. No signup required.
What should I archive for campaign QA?
Keep the final packaged creative, publisher specification used, preview captures, click destination, disclosure version, test results and the served-versus-viewable reporting definitions.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.




