How to Check Image Dimensions

Knowing an image’s exact pixel dimensions is the first step in almost every design and web workflow: confirming a source file is large enough for a planned use, calculating aspect ratio for a crop, verifying print output at a required DPI, or debugging a layout that looks mysteriously soft. Most operating systems show dimensions in a right-click info panel, but a dedicated tool is faster for batches and shows the data alongside aspect ratio, DPI, and file weight. This guide explains what the dimensions actually tell you, how DPI and pixel count relate, and which sizes to remember for common web and print targets.

What width and height really mean

Width and height describe the image as a grid of pixels. A 1920 × 1080 file has 1920 columns and 1080 rows, for a total of 2,073,600 pixels — just over 2 megapixels. This grid is the raw data; it says nothing about how large the image appears when printed or rendered on screen.

Every other number you might see — inches, centimeters, points, DPI — is derived from the pixel grid plus some assumed or declared output size.

Aspect ratio from dimensions

Divide width by height, simplify, and you have the aspect ratio. 1920/1080 simplifies to 16:9. 1200/800 simplifies to 3:2. Knowing the aspect ratio matters because it determines whether the image can fit a target frame without cropping or letterboxing.

Common ratios to recognize at a glance:

• 1:1 — square, Instagram feed, profile avatars.
• 4:3 — classic digital camera, older monitors, presentations.
• 3:2 — 35mm film, DSLRs, standard prints.
• 16:9 — HD video, YouTube thumbnails, modern laptop screens.
• 9:16 — vertical video, Stories, Reels, TikTok.
• 21:9 — ultrawide cinema, hero banners.

Pixels versus DPI versus physical size

Pixels per inch (PPI, often loosely called DPI) translates between pixel grid and physical size. A 3000 × 2000 image at 300 PPI prints cleanly at 10 × 6.67 inches. The same file at 72 PPI “prints” at 41.67 × 27.78 inches but will look pixelated.

For on-screen display, DPI metadata is almost always ignored: browsers and screens care about pixels, not declared inches. You can freely change the PPI tag without resampling the image; only the print size claim changes, not a single pixel of data.

Reading metadata: the difference between stated and actual

A file’s header can claim any dimensions it likes; a good checker measures the actual pixel grid. Occasionally you’ll find files where the metadata disagrees with reality — usually because a tool resized the pixels but forgot to update the header, or vice versa. Trust the actual pixel count.

Tools typically also expose: file size in KB/MB, color depth (8-bit, 16-bit), color space (sRGB, Adobe RGB, Display P3), and transparency flag (PNG alpha channel).

Minimum dimensions for common uses

• Instagram feed post: at least 1080 × 1080.
• Instagram story/Reel: 1080 × 1920.
• YouTube thumbnail: 1280 × 720 minimum, 1920 × 1080 recommended.
• Facebook link preview: 1200 × 630.
• Twitter/X in-stream photo: 1200 × 675.
• LinkedIn post image: 1200 × 627.
• Blog hero banner: 1920 × 1080 works on most layouts.

Keeping these in your head saves a hundred back-and-forths with designers.

Print-ready sizes

For a 300 PPI print — the standard for photo prints, business cards, and most professional print work — multiply inches by 300 to get minimum pixel dimensions:

4x6 print:    1200 x 1800 px
5x7 print:    1500 x 2100 px
8x10 print:   2400 x 3000 px
11x17 poster: 3300 x 5100 px
Business card (3.5x2): 1050 x 600 px

Newspapers accept 150–200 PPI because of the rougher paper stock; large-format banners tolerate 100 PPI or less because you view them from a distance.

Viewing distance and perceived sharpness

DPI requirements assume normal reading distance (about 12 inches / 30 cm for a print, an arm’s length for a phone). A highway billboard printed at 20 DPI looks crisp at 100 meters. A product box printed at 300 DPI looks crisp at 1 meter. The rule of thumb: halve the DPI for every doubling of viewing distance.

This is why dimensions alone don’t determine quality; context of use does.

Responsive web sizing

For web images, the right pixel dimensions depend on CSS rendered width and device pixel ratio. If a CSS pixel is 400 wide on a DPR-2 device, you need 800 hardware pixels of source. Checking the original’s dimensions tells you how much upscaling — if any — you’ll be forced to do for retina displays.

A quick audit: take your hero image’s intrinsic width, divide by its painted CSS width, and if the ratio is below 2 you’re delivering soft visuals to retina users.

Why dimensions matter for SEO

Search engines parse intrinsic dimensions to build image indexes and to detect whether an image is worth showing at all. Too-small images (below ~300 × 200) are often skipped entirely. Too-large images that never get resized can be a ranking signal against page speed.

Declaring width and height attributes in the HTML also prevents layout shift, which is a Core Web Vitals metric. Those values should match the intrinsic dimensions of the source file.

Checking many files at once

When auditing a folder of uploads, a batch dimension checker produces a table with filename, width, height, aspect ratio, DPI, and file size. Sort by smallest height to find images too tiny for hero use; sort by file size to find bloat; filter by aspect ratio to find anything that won’t fit a fixed layout. The same report on a weekly cadence is a great way to catch uploads that slipped past your content guidelines.

Reading dimensions on different platforms

Quick ways to check a single file without opening a tool:

• macOS Finder: select a file, press spacebar for Quick Look; press Cmd+I for full Info with dimensions.
• Windows Explorer: right-click, Properties, Details tab shows width and height.
• Linux: file image.jpg or identify image.jpg (ImageMagick) from the terminal.
• Web browser: right-click any image on a loaded page and pick “Inspect” — DevTools shows rendered and intrinsic size.

Dedicated tools become worth it when you need aspect ratio, DPI, and color profile alongside dimensions, or when you’re processing a batch.

Megapixels and what the number really means

Megapixels (MP) is just width × height divided by a million. A 24 MP camera produces 6000 × 4000 images. The headline number tells you the maximum print size at a given DPI but nothing about sensor quality, lens sharpness, or low-light performance. A 12 MP iPhone photo often looks better than a 48 MP photo from a cheap camera because other factors dominate.

For web, anything over 4–8 MP is surplus. For print, 12–16 MP comfortably covers up to 11 × 14 inches at 300 DPI.

Declaring dimensions in HTML

Always include width and height attributes on <img> elements, even if CSS will resize them. The attributes tell the browser the intrinsic aspect ratio so it can reserve the correct box before the image loads, preventing layout shift:

<img
  src="/hero.jpg"
  width="1200"
  height="630"
  alt="Team photo"
/>

The numbers should match the source file’s actual pixel dimensions. CSS will still determine the rendered size; the attributes just communicate the ratio.

Dimension mismatches in production

Common symptoms that trace back to a dimension problem:

• Blurry hero image on retina displays: source intrinsic width is too close to the CSS painted width.
• Visible layout shift: missing width and height attributes force the browser to reflow after the image loads.
• Squished or stretched avatar: the source isn’t square but the CSS forces a 1:1 container without object-fit: cover.
• Slow product grid: originals are 4000 px wide, delivered to tiles that paint 300 px.

Debug by comparing intrinsic dimensions (what the file is) to rendered dimensions (what the browser paints). The DevTools Network panel shows both.

Common mistakes

Confusing DPI with pixel count: changing a JPEG’s DPI tag from 72 to 300 in Preview does not add a single pixel — it just relabels the file. The image will not print any sharper unless you actually resample it. Another common mistake: trusting the screenshot dimensions reported by tools on macOS Retina displays, which sometimes show logical (CSS) pixels and sometimes hardware pixels. Verify the actual file on disk to be sure. Finally, confusing landscape 1920 × 1080 with portrait 1080 × 1920 when uploading to a platform that silently crops the mismatched orientation — always check which dimension the platform wants first.

Run the numbers

Drop any file into our image dimensions checker to get pixel width, height, aspect ratio, DPI, and file size in one view. When the dimensions are wrong for your target, the image resizer is the fix. For working out whether a given width and height can fit a layout ratio, the aspect ratio calculator does the math instantly.