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 reinstallThere is no single best pixel size for every image on a website. Choose dimensions for the image’s role and its displayed space: a full-width hero, a small thumbnail, a logo, and a social link preview have different shapes and needs. For ordinary page images, provide responsive variants so browsers can select an appropriate file; for a broad social-sharing starting point, use 1200 × 630 pixels and check the destination’s own rules.
How to choose website image dimensions
Start with the image’s job, not a universal site-wide number. A content image may need to fit an article column, while a card thumbnail may be cropped to a fixed ratio. A logo is often constrained by its design and transparent margins; a hero may span a much wider area. Social previews are controlled partly by the receiving platform, not just by the dimensions of the image on your page.
Use the rendered slot as the baseline. If an image appears 600 CSS pixels wide, a 600-pixel-wide file may look adequate on a standard-density display, while a higher-density display can benefit from a larger variant. That does not mean every image should be uploaded at the largest size available: oversized files add bytes without necessarily improving the visible result. The right dimensions depend on display width, crop, pixel density, and the content’s detail.
- Identify the slot’s expected width and aspect ratio at each relevant layout breakpoint.
- Decide whether the image must preserve its full frame or can be cropped to fill the slot.
- Prepare suitable width variants and let responsive HTML communicate the choices.
- Check the page at the actual sizes and crops used by its template and destinations.
Google Search Central’s image guidance describes responsive delivery and general image practices; it does not prescribe one pixel size for every website placement. Consequently, site-builder presets, CMS thumbnail crops, advertising placements, and theme-specific banners should be checked in their own documentation rather than inferred from the examples below.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsPractical dimensions by placement
| Placement | Dimensions or guidance | How to interpret it |
|---|---|---|
| Responsive content image | No universal fixed dimensions. Google’s examples include candidate widths of 320, 480, and 800 px. | These are examples, not prescribed targets. Choose variants around your actual layout widths and use srcset and sizes. |
| General social link preview | 1200 × 630 px, approximately 1.91:1. | URLpipe’s 2026 guide presents this as a practical cross-platform starting point, not a guarantee of identical display on every service. |
| LinkedIn website share | Minimum 1200 × 627 px; recommended ratio 1.91:1; maximum file size 5 MB. | These are LinkedIn Help specifications. LinkedIn says images under 401 px wide display as thumbnails. Its help page labels itself as last updated two years before the 2026 access noted in the source material; verify current details if they are critical. |
| Instagram feed post | Hootsuite’s September 2026 guide reports 1080 px width and supported ratios from 1.91:1 to 4:5. | The guide says images outside that range are cropped. Feed and profile-grid presentation may differ; these are secondary-reference recommendations, not website image rules. |
| Instagram Stories and Reels | 1080 × 1920 px (9:16). | Hootsuite’s September 2026 quick reference. Keep important content clear of interface overlays and safe-area edges. |
| Facebook feed post | Landscape 1080 × 566, portrait 1080 × 1359, or square 1080 × 1080 px. | Hootsuite’s secondary reference; select the shape for the intended placement and crop. |
| X in-stream photo | Landscape 1280 × 720, vertical 720 × 1280, or square 1080 × 1080 px. | Hootsuite’s September 2026 reference, not an official current X specification. |
These social figures are not interchangeable rules for website hero images, thumbnails, ad units, or every organic post. A recommendation from a third-party guide is also not the same thing as an official platform minimum. Where the destination matters, check its current official documentation and preview the actual crop.
#1 Best Overall
- HTML CSS Design and Build Web Sites
- Comes with secure packaging
- It can be a gift option
Serve responsive images with HTML
For a layout that displays an article image at a range of widths, provide candidate files in srcset, describe the expected rendered width with sizes, and retain a fallback in src. The browser can use that information to select a suitable candidate. The widths and file names below are illustrative; they must correspond to image files you actually generate.
<img
src="/images/river-800.jpg"
srcset="/images/river-320.jpg 320w,
/images/river-480.jpg 480w,
/images/river-800.jpg 800w,
/images/river-1200.jpg 1200w"
sizes="(max-width: 600px) 100vw,
(max-width: 1000px) 80vw,
800px"
width="1200"
height="800"
alt="A river winding through a forested valley">
The width descriptors such as 800w describe each candidate’s intrinsic pixel width. The sizes value describes the image’s expected CSS display width under the listed conditions; it does not resize the image itself. Adjust the breakpoints and slot widths to match your layout. The width and height attributes communicate the image’s intrinsic dimensions and help reserve its aspect ratio before it loads; use values that match the fallback file’s proportions.
When to use picture
Use <picture> when you need to group alternate formats or art-directed sources, such as a different crop for a narrow screen. Keep an <img> inside it as the fallback.
<picture>
<source
type="image/avif"
srcset="/images/river-480.avif 480w,
/images/river-800.avif 800w"
sizes="(max-width: 600px) 100vw, 800px">
<source
media="(max-width: 600px)"
srcset="/images/river-portrait-480.jpg 480w,
/images/river-portrait-800.jpg 800w"
sizes="100vw">
<img
src="/images/river-800.jpg"
width="1200"
height="800"
alt="A river winding through a forested valley">
</picture>
Order sources deliberately: browsers use the first matching source they can handle. Keep a valid fallback URL in src, since not every browser or crawler understands responsive attributes in the same way.
Aspect ratio, crop, and image quality
Dimensions alone do not determine whether an image fits. Aspect ratio is width divided by height: 1200 × 630 is about 1.91:1, while 1080 × 1920 is 9:16. If a slot has a different ratio from the source, a layout may leave empty space, distort the image, or crop it. Avoid distortion. For a fixed card or preview, decide what may be cropped and keep essential text, faces, or product details inside the portion likely to remain visible.
For CSS-controlled crops, a common pattern is object-fit: cover, which fills the box while cropping excess. The focal point can be adjusted with object-position. Use object-fit: contain when the entire image must remain visible, accepting unused space if the shapes differ. These CSS behaviors do not change the source file’s pixel dimensions; they change how it is fitted into its display box.
Rank #3
Google Search Central recommends an image that is relevant and representative of the page, and says to use high resolution if possible. “High resolution” is not a universal instruction to use the largest possible file: select enough pixels for the rendered size and likely display density, then optimize the file. Google also cautions that images can contribute substantially to page size, affecting load speed and data use.
Choose image formats and useful metadata
Google Search supports BMP, GIF, JPEG, PNG, WebP, SVG, and AVIF images referenced in an img element’s src. Match the filename extension to the actual file type. The format should suit the content and delivery needs: photographic images, transparency, animation, and vector artwork do not all have the same requirements. Compare visual quality and file weight after export rather than assuming a format or dimension is automatically optimal.
- Write concise, contextual
alttext for images that convey information. For purely decorative images, use an emptyaltvalue so assistive technology can skip them. - Use descriptive filenames that identify the subject without turning them into keyword lists.
- For a preferred search or social image, choose a representative image rather than a generic site logo or an image dominated by text, and avoid extreme ratios.
- Check that the delivered file is not dramatically larger than its displayed role requires.
Set a preferred Open Graph image
Open Graph metadata lets a page specify a preferred image for link previews. Google’s image guidance documents og:image as one way to identify a preferred image and advises choosing one that represents the page. A 1200 × 630 px canvas is a practical broad-sharing starting point, but services may crop, compress, or apply their own limits. LinkedIn’s documented minimum is 1200 × 627 px, its recommended ratio is 1.91:1, and its stated maximum file size is 5 MB.
Rank #4
- Brand: Wiley
- Set of 2 Volumes
- A handy two-book set that uniquely combines related technologies Highly visual format and accessible language makes these books highly effective learning tools Perfect for beginning web designers and front-end developers
<meta property="og:image" content="https://example.com/images/article-share.jpg">
Replace the example URL with an absolute URL to the image you publish. The page’s image for social sharing need not be the same crop or file used inside the article. Check the rendered preview on the target service when the crop is important; a correct metadata value cannot force every platform to show the same framing.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Check the rendered result on your site
Inspect the actual page at representative viewport widths, including a narrow phone layout and a wider desktop layout. Check whether the browser-selected image is sharp enough, whether the crop preserves the subject, and whether the page reserves space while the image loads. Also inspect the social preview separately: the in-page image and the metadata-selected preview can be different assets.
A browser screenshot is useful for reviewing layout and crop, but it does not by itself prove which source file the browser selected or reveal every image’s intrinsic dimensions. For those details, inspect the element and network request in browser developer tools. ScreenshotNeo is a website screenshot API and MCP server that can capture rendered pages; it can complement, not replace, checking the image element and its loaded asset.
Best Value
Or skip the browser setup
To capture a page for a visual layout check, make one GET request. Replace the URL with the page you are reviewing and put your API key in place of YOUR_API_KEY. See the ScreenshotNeo API documentation for request options.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com -o shot.webp
ScreenshotNeo accepts cookie or consent banners like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each of those steps can be turned off. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, and response headers identify the page verdict and billing status. Its 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 shots per month with no card; paid plans start at $5 for 3,000 shots. See ScreenshotNeo for product details, or sign up free.
Troubleshoot common image-size problems
- The image looks blurry. Check the selected candidate and its intrinsic width against the rendered slot and display density. Make sure
srcsetdescriptors correctly match the files, and that the source was not already enlarged from a smaller original. - The subject is cut off. Compare the source and slot ratios, then adjust the crop or focal point. For social posts, confirm the current platform’s supported range rather than assuming the website crop will carry over.
- The wrong responsive file appears. Verify that every candidate URL loads, that each
wdescriptor is accurate, and thatsizesreflects the actual CSS slot. A misleading slot description can lead the browser to choose an unsuitable candidate. - The page jumps when the image loads. Supply accurate intrinsic
widthandheightattributes or reserve a matching aspect ratio in CSS. - The preview is missing or cropped unexpectedly. Confirm that the
og:imageURL is publicly accessible and points to the intended file. Then check the receiving platform’s documented dimensions and its preview behavior. - The page is heavy or slow to load. Review the delivered image’s dimensions and file weight, provide responsive candidates, and avoid sending a large source to a small slot when a suitable smaller variant can be served.
FAQ
Should every image on a website use the same dimensions?
No. A shared size can force unnecessary crops or waste bandwidth because image roles and display slots differ.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Is 1200 × 630 the official Open Graph size for every platform?
No. It is a practical cross-platform recommendation cited by URLpipe, not a universal platform requirement. LinkedIn’s documented minimum is 1200 × 627 px.
Can I use one image file with responsive HTML?
Yes, but if that file is substantially larger than the slot needs, it can transfer more data than necessary. Candidate files let the browser choose among available widths.
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.




