There is no single, evidence-backed aspect ratio for every website banner. Use the requirements for the exact hero, banner, or CMS component first. As a documented example, Brandeis University’s Heller School specifies 16:9 for banner photos, while Google advertising placements use different, platform-specific assets such as 1200 × 628 pixels (1.91:1) for horizontal responsive display ads. Those advertising numbers should not be treated as a universal website-hero standard.
Start with the component specification
A banner is not a single technical format. It might be a homepage hero, a narrow announcement strip, a blog header, a commerce category image, or an advertising creative. Each is cropped and rendered differently. Before exporting an image, identify the component that will display it and check its documented:
- Accepted aspect ratios or maximum height.
- Recommended and minimum pixel dimensions.
- Desktop, tablet, and mobile crop behavior.
- Whether the image uses
cover,contain, focal-point controls, or a fixed height. - File-type, file-size, and transparency limits.
If the theme or builder gives a required ratio, follow it even when it differs from common examples. A 16:9 source can be cropped into a much wider hero, and a 1.91:1 advertising asset can be unsuitable for a tall mobile banner.
Aspect ratio and pixel dimensions are different
An aspect ratio describes relative width and height. Pixel dimensions describe the actual raster size. A 16:9 image can be 1600 × 900, 1920 × 1080, or 1280 × 720; all have the same ratio. The larger files contain more pixels but may also cost more bandwidth.
Recommended Free Tools
Calculate the missing dimension with these formulas:
- Height from width: height = width × (ratio height ÷ ratio width).
- Width from height: width = height × (ratio width ÷ ratio height).
For example, a 1600-pixel-wide 16:9 image is 900 pixels high. A 1200-pixel-wide 1.91:1 image is approximately 628 pixels high, matching Google’s published horizontal advertising example.
Documented ratios and dimensions
| Use case | Ratio | Published dimensions | How to interpret it |
|---|---|---|---|
| Brandeis Heller School banner photos | 16:9 | Not stated | An institution-specific web banner example, not a universal standard. Brandeis photo standards |
| Google responsive display ad, horizontal | 1.91:1 | 1200 × 628 recommended; 600 × 314 minimum | Advertising specification only. Google Ads Help |
| Google Performance Max marketing image, landscape | 1.91:1 | 1200 × 628 | Marketing-asset requirement for that campaign type. Google for Developers |
| Google Performance Max marketing image, square | 1:1 | 1200 × 1200 | A separate advertising variant, not a standard website hero. |
The table shows why a generic “best banner size” answer is misleading: the same word, banner, covers different implementations.
Choosing a practical source for a normal website hero
When the theme says 16:9
Prepare a 16:9 master and compose the subject so it survives the component’s crop. Brandeis University’s Heller School uses 16:9 for its banner photos, which is a useful reference when your own specification is silent, but it remains an example rather than a web-wide rule.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →When the component is unusually wide
A panoramic hero may be closer to 2:1 or wider. Do not force a 16:9 image into it without checking the result: the top and bottom may disappear when the browser uses a cover crop. Export to the component’s stated ratio, or supply a desktop-specific crop if the CMS supports variants.
#1 Best Overall
- HTML CSS Design and Build Web Sites
- Comes with secure packaging
- It can be a gift option
When the image is an advertisement
Use the advertising platform’s specification. Google recommends 1200 × 628 pixels at 1.91:1 for a horizontal responsive display image, with 600 × 314 as the minimum. Performance Max also lists 1.91:1 landscape images at 1200 × 628 and 1:1 square images at 1200 × 1200. These values govern those ad placements, not ordinary site headers.
Design for responsive cropping
Responsive layouts change the visible window, even when the source file stays the same. A desktop hero may be wide and shallow; a phone may display a narrower slice or a taller block. Put faces, products, logos, and essential words in the central area unless the component documents a different focal point. Avoid placing critical details against the extreme edges.
Rank #2
Do not assume a universal “safe-area percentage” for website banners; the reviewed standards do not establish one. Instead, preview the real component at the breakpoints your site uses.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesProvide variants when the system allows them
- Create a desktop crop and a mobile crop when the CMS supports responsive sources or art direction.
- Keep the subject’s position consistent enough that a crop does not appear to jump unexpectedly.
- Test with long headlines, navigation overlays, and translated text, since these can cover more of the image than the original layout.
- Check both high-density and ordinary displays. A small source can look soft when rendered at a larger CSS size.
A repeatable banner-sizing workflow
- Name the placement. Record the page, component, and whether it is a hero, strip, card, or ad.
- Read the implementation settings. Look in the theme documentation, CMS field help, or component code for ratio, dimensions, focal-point, and crop rules.
- Choose the master ratio. Use the stated ratio. If none is stated, select a ratio that matches the component’s measured box and label the choice as a project decision, not a standard.
- Calculate pixels. Export enough pixels for the largest displayed size while staying within the site’s file-size guidance.
- Compose for the crop. Keep important content away from edges and leave room for overlaid text where the design requires it.
- Export variants. Supply mobile or square versions when the platform accepts them; use the Google dimensions only for Google advertising placements.
- Preview in the real page. Inspect desktop, tablet, and phone widths, including the smallest supported viewport.
- Measure the result. Check loading time, visual sharpness, text contrast, and whether lazy loading or overlays hide the subject.
Implementing the image without accidental distortion
Preserve the source ratio rather than stretching it. A typical responsive image can use a width constrained by its container and an automatic height. For a fixed-height hero, the design normally needs a deliberate crop rather than distortion; verify the component’s CSS and focal-point controls. If text is part of the banner, an HTML overlay is usually easier to adapt than baking the words into one raster image.
Use the site’s supported modern format when available, retain a fallback if required, and keep filenames and alternative text meaningful. Decorative images can use empty alternative text; an image conveying information needs a concise description. These implementation decisions are independent of whether the source is 16:9 or 1.91:1.
Common mistakes and fixes
“1200 × 628 is the best website banner size”
Cause: an advertising specification has been generalized to every hero image. Fix: reserve 1200 × 628 (and its 600 × 314 minimum) for the Google placements that specify it; obtain the website component’s own ratio for a normal page banner.
The subject is cut off on phones
Cause: a single wide crop is being used in a narrow viewport. Fix: move the focal subject inward, configure the component’s focal point, or provide a mobile-specific source.
The image looks stretched
Cause: width and height are forced to unrelated values. Fix: preserve the intrinsic ratio and use intentional cropping rather than non-proportional scaling.
The file is sharp but the page is slow
Cause: a large master is downloaded where a smaller rendered size would do. Fix: generate appropriately sized responsive variants, compress them within the site’s quality requirements, and avoid loading a below-the-fold banner eagerly.
Text becomes unreadable over the image
Cause: a crop or background change removes the contrast planned for the original composition. Fix: add a controlled overlay, reposition the text, or use a separate crop with a quieter background.
Rank #4
Verify the finished page with a screenshot
Manual browser checks remain useful: open the page at representative viewport widths, wait for lazy-loaded content, and inspect the banner after cookie dialogs and chat widgets are handled. For repeatable checks in a build or QA process, capture the rendered page rather than judging the source file alone.
Or skip the browser setup
ScreenshotNeo is a website screenshot API and MCP server. One GET request can capture a URL as PNG, JPEG, WebP, or PDF, so you can inspect the actual responsive crop after deployment.
cURL:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpPython:
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)Node.js:
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);See the complete option list and request details in the ScreenshotNeo documentation. It can load lazy images, capture a CSS-selected element, set a viewport or device preset, use a retina scale, wait for a selector, delay, or network idle, and hide overlays. Before capture it accepts consent banners and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each step can be disabled. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and response headers identify the page verdict and billing status. Its MCP server provides take_screenshot, get_page_info, and capture_pdf for Claude, Cursor, and other MCP clients. The Free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 shots.
Create a free ScreenshotNeo account to test your banner without adding a card.
Cost, reliability, and maintenance considerations
- Keep the original, uncropped master so you can create new variants when a theme changes.
- Record the component ratio and export dimensions beside each asset; this prevents an ad specification from silently becoming a site-wide rule.
- Recheck banners after redesigns, breakpoint changes, cookie-consent updates, and headline changes.
- For automated screenshots, distinguish a failed page from a valid capture before storing it in visual-regression results. ScreenshotNeo exposes page-verdict and billing headers for that purpose.
Frequently Asked Questions
What is the safest default if my website gives no banner guidance?
Measure the rendered component, choose a ratio that matches its intended crop, and document that choice. A 16:9 banner is a defensible example because Brandeis University’s Heller School uses it, but it is not a universal requirement.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallShould I use the same image for a website hero and a Google ad?
Not automatically. Google ad placements have their own 1.91:1 and 1:1 specifications, while a website hero follows its component’s layout. Create separate crops when the display windows differ.
How can I tell whether a banner crop works on mobile?
Preview the live component at the smallest supported viewport and at common desktop widths, checking faces, products, logos, and overlaid text after all page overlays have loaded.
Quick Recap
The Bottom Line
Use the website component’s documented ratio first. Treat 16:9 as an institution-specific web example and 1200 × 628 at 1.91:1 as a Google advertising specification—not as a universal website banner rule.
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.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →
