Recommended Free Tools
There is no universal pixel size for a full-page website background. Choose an image that has enough pixels for the largest area you will render, compose it around the subject that must remain visible, and test the crop at representative viewport shapes. In most full-bleed designs, background-size: cover is the practical default: it fills the area while preserving the image ratio, but it can crop an edge. Use contain only when showing the entire source matters more than filling every pixel.
The right file therefore depends on the page area, expected viewport range, focal point, and performance budget—not a fixed target such as “1920×1080.”
What “full-page background size” actually means
A bitmap has intrinsic dimensions, such as 2400×1600 pixels, and an aspect ratio of 3:2. CSS paints that bitmap into an element’s background positioning area. The element might be a 1440×900 desktop viewport, a 390×844 phone viewport, or a hero section whose height changes with its content. The browser scales the source against that area according to background-size; it does not look for a universal website-background number.
Because viewport width and height vary independently, the same source can show a wide horizontal crop on a desktop and a much tighter vertical crop on a phone. A source that looks perfect in a design mock-up can hide a person, product, or text-safe area when the browser shape changes.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →#1 Best Overall
- HTML CSS Design and Build Web Sites
- Comes with secure packaging
- It can be a gift option
Choose between cover and contain
| Decision axis | cover |
contain |
|---|---|---|
| Fills the area edge to edge | Yes | Not always |
| Entire source remains visible | Not guaranteed | Yes, unless another rule clips it |
| Cropping | Possible when aspect ratios differ | Avoided |
| Uncovered space | Avoided | Possible; the element’s background color or a repeat may show |
| Typical use | Decorative full-bleed backdrop | Logos, diagrams, or artwork that must be seen whole |
How cover scales
With cover, the browser chooses the smallest scale that makes both the rendered image width and height at least as large as the container. If the source is wider than the area, the excess is cut from the sides; if it is taller, the excess is cut from the top and bottom. The image’s proportions stay intact.
.page {
background-image: url('/images/site-bg-2400.webp');
background-size: cover;
background-position: center;
background-repeat: no-repeat;
}background-position controls which part survives the crop. For a subject near the right edge, try right center or a percentage such as 70% 50% rather than accepting the default center.
How contain scales
contain chooses the largest scale that keeps both image dimensions inside the area. No source pixels are removed, but one axis can leave unused space. Set a deliberate background color so that the letterbox area looks intentional.
.illustration {
background-color: #111827;
background-image: url('/images/diagram.png');
background-size: contain;
background-position: center;
background-repeat: no-repeat;
}A practical method for selecting dimensions
- Define the painted area. Decide whether the background belongs to the entire document, a hero, a card, or another element. Record the smallest and largest viewport widths and heights that your layout supports. A “full page” that means a 700-pixel hero needs a different source than a background on a 3000-pixel-tall landing page.
- Choose the visibility rule. If edge-to-edge coverage is mandatory, start with
coverand plan for cropping. If every mark or edge in the artwork must remain visible, start withcontainand design the surrounding color or pattern for the possible empty area. - Prepare the composition for the crop. Keep the focal subject away from edges that may disappear. Leave a quieter region where navigation or headline text will sit. Do not place a face, logo, or product at the exact center unless you know the center crop is safe at every target shape.
- Estimate a sensible source resolution. Export enough pixels for the largest rendered use and the display density you intend to support, but do not send a huge desktop bitmap to every phone. The evidence does not establish one universal pixel dimension or file-weight target; measure your actual layout and tune from there.
- Add responsive variants when the design changes. Use a smaller file for narrow screens when the desktop source would waste bytes, and use a separately composed mobile crop when the subject needs different framing. A media query can select the appropriate asset.
- Inspect real viewport shapes. Check at least one wide desktop, one short laptop, one tall phone, and one tablet-like shape. Also test an unusually tall or narrow window; these often reveal hidden focal points sooner than standard presets.
Responsive background patterns
When the same composition works at every width, a single source can be simplest:
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →.landing {
min-height: 100svh;
background: url('/images/landing-2400.webp') center / cover no-repeat;
}If mobile needs a different crop or a lighter file, switch the source at a breakpoint chosen from your layout rather than from a universal rule:
.landing {
min-height: 100svh;
background: url('/images/landing-desktop.webp') 62% center / cover no-repeat;
}
@media (max-width: 700px) {
.landing {
background-image: url('/images/landing-mobile.webp');
background-position: 48% center;
}
}The breakpoint is a design decision. Select it where your composition or layout changes, then verify the transition around that width instead of assuming a particular phone pixel size.
Rank #2
Use focal-point positioning deliberately
Percentages map the image’s position to the container. For example, background-position: 25% 50% keeps the left-side subject nearer the visible center than center would. You can use separate horizontal and vertical values, or a length such as background-position: 40px top when a fixed offset is more predictable. Recheck the result after changing the source crop; the same percentage does not guarantee the same subject placement across files.
When an image should be an img or picture
Backgrounds are a good fit for decorative layers, color washes, and artwork behind readable HTML. If the image is meaningful content—such as a product photograph, news image, or diagram—an img or picture element gives you semantic alternative text and responsive source selection.
<picture>
<source media='(max-width: 700px)' srcset='/images/hero-mobile.webp'>
<img src='/images/hero-desktop.webp' alt='A red bicycle beside a mountain road'>
</picture>Responsive markup also exposes the image to the browser’s preload scanner. CSS background images are not discovered by that scanner, so a visually dominant background can begin loading later than an equivalent image element. If the background is the main meaningful image in the initial view and contributes to the largest contentful paint, consider an image element or a responsive preload strategy. Keep a CSS background for decorative imagery or layered effects where semantics are not needed.
Resolution, density, and file weight
Provide enough pixels without overserving
A source rendered at 1200 CSS pixels wide generally needs fewer physical pixels on a standard-density display than on a high-density display, but the required quality depends on the crop and viewing distance. Instead of multiplying every dimension blindly, export a small set of tested widths and let responsive rules choose among them. Compare the sharpness of the focal subject at the largest crop your layout permits.
Choose a format for the artwork
- WebP or another modern compressed format: often a practical default for photographic backgrounds when your browser support policy allows it.
- JPEG: useful for photographs where transparency is unnecessary.
- PNG: appropriate for transparency or sharp, limited-color graphics, but potentially heavy for photos.
Compress each responsive variant separately. A smaller mobile composition can be substantially lighter than a desktop file; one web.dev demonstration reports its mobile background file as 67% smaller than its desktop file, but that is a demo-specific comparison, not a universal saving target.
Account for overlays and contrast
A dark or translucent overlay can preserve text contrast without changing the source crop:
.hero {
background-image:
linear-gradient(rgb(0 0 0 / 0.42), rgb(0 0 0 / 0.42)),
url('/images/hero.webp');
background-position: center;
background-size: cover;
}Check the actual heading, links, and focus indicators against the lightest part of the image. Do not rely on a single screenshot if the crop changes by viewport.
Implementation checklist
- Set a fallback background color so text remains readable while the image loads or if it fails.
- Use
background-repeat: no-repeatfor a single full-page image unless tiling is intentional. - Specify
background-positionrather than accepting a focal point that happens to look right in one viewport. - Keep unrelated width and height declarations off the image itself; independently forcing both can stretch it.
- Use
min-height: 100svhor an appropriate section height when the design should cover the visible screen, while allowing content to extend beyond it. - Respect user preferences such as
prefers-reduced-motionif you add animated background effects; a static image itself does not need motion.
Test the crop before you publish
- Open the page in browser developer tools and toggle responsive device mode.
- Record the image’s visible focal point at a wide desktop, a short desktop, a tall phone, and a tablet width.
- Temporarily outline the background element to confirm which box is being covered; a parent with unexpected height is a common source of “wrong size” reports.
- Resize around your media-query breakpoint and look for a sudden subject jump, a headline over a busy area, or an uncovered strip.
- Throttle the network and reload. Confirm that the fallback color, text contrast, and layout remain usable before the image arrives.
- Inspect the delivered file size and format in the Network panel. If a phone downloads the desktop original despite a mobile rule, check URL paths, cache state, and selector specificity.
Troubleshooting common sizing problems
The subject is cut off
This is normal cover behavior when the source and container ratios differ. Move the focal point with background-position, create a mobile-specific crop, or switch to contain if showing the entire subject is mandatory.
There are blank bands around the image
You are likely using contain, a repeated rule was disabled, or the element’s ratio is different from the source. Set a matching background color, use cover when cropping is acceptable, or choose a source composed for that area.
The image looks stretched
Check for CSS that sets independent width and height on an image element, or for a non-background implementation that forces both dimensions. Background cover and contain preserve the source ratio; arbitrary dimensions may not.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows 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 reinstallThe background is blurry on a large monitor
Inspect the rendered size and the intrinsic dimensions of the delivered file. If the browser must enlarge it beyond its useful resolution, provide a larger variant. If it is sharp but slow, keep the resolution and reduce compression cost only after checking the focal detail.
The phone loads a heavy desktop file
Verify that the mobile media query changes background-image, not only position. Confirm the browser is not serving a cached desktop response and that the mobile URL is reachable. Separate art-directed files are often more efficient than shrinking a single oversized source in CSS.
Rank #4
The hero appears late in performance tests
CSS backgrounds are not found by the preload scanner. If this image is meaningful and is the largest contentful element, use responsive img/picture markup or an appropriate preload strategy. If it is decorative, keep it as a background and prioritize readable content.
Or skip the browser setup
To inspect how a page actually renders at different viewport settings, ScreenshotNeo provides a website screenshot API and MCP server for developers. One GET request returns a PNG, JPEG, WebP, or PDF; its options include full-page capture with lazy images loaded, device presets or custom viewports, retina scale, dark mode, custom CSS and JavaScript, selector-based waits, and mobile or desktop headers. See the ScreenshotNeo documentation for the current parameter names.
Use this call to capture a page while you compare your background crop:
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}`);Before the capture, ScreenshotNeo accepts cookie or consent banners like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each cleanup step can be turned off. Bot checks and CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, and the response reports the page verdict and billing status in X-Page-Verdict and X-Billed headers. An MCP server exposes take_screenshot, get_page_info, and capture_pdf to Claude, Cursor, and other MCP clients.
| Plan | Included shots | Price |
|---|---|---|
| Free | 1,000 per month | $0, no card |
| Starter | 3,000 | $5 |
| Growth | 15,000 | $15 |
| Pro | 60,000 | $39 |
| Scale | 250,000 | $99 |
| Business | 1,000,000 | $249 |
Every feature is available on every plan, and yearly billing gives two months free. Create a free ScreenshotNeo account to get 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 shots.
Frequently Asked Questions
Should a full-page background use fixed attachment?
Only when the visual effect is intentional and tested on your supported mobile browsers. background-attachment: fixed changes scrolling behavior and can affect performance or usability; it does not solve image sizing or cropping.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsCan I calculate one exact source width from my monitor resolution?
No. Monitor resolution describes one display, while your CSS area, viewport height, device density, and crop determine the rendered result. Select and test responsive sources against the layouts you actually support.
How do I keep a background from reducing text readability?
Reserve a low-detail text area in the composition, add a tested overlay or solid panel, and verify contrast at every representative crop. Positioning alone cannot guarantee readable text.
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.
