Free · Fast · Privacy-first

Crop Image to Precise Pixels

Some image destinations demand exact pixel dimensions: a profile picture must be exactly 400 by 400, a YouTube thumbnail exactly 1280 by 720, a website hero exactly 1920 by 800.

⚡

Type exact width and height

🔒

No rounding errors

✨

Reposition without resizing

⚡

Works on any device

Cost: Free forever
Sign-up: Not required
Processing: In your browser
Privacy: Files stay local

FreeNo signupWhite-label

Add this Image Cropper to your website

Drop the Image Cropper into any page — blog post, product docs, intranet, school portal — with a single line of HTML. Your visitors get the full tool, processed entirely in their browser. No backend, no uploads, no signup.

Files stay 100% in the visitor's browser
Responsive — adapts to any container width
Free forever, no API key needed

Embed code

<iframe
  src="https://www.fixtools.io/image-tools/image-cropper?embed=1"
  width="100%"
  height="780"
  frameborder="0"
  style="border:0;border-radius:16px;max-width:900px;"
  title="Image Cropper by FixTools"
  loading="lazy"
  allow="clipboard-write"
></iframe>

<iframe
  src="https://www.fixtools.io/image-tools/image-cropper?embed=1"
  width="100%"
  height="780"
  frameborder="0"
  style="border:0;border-radius:16px;max-width:900px;"
  title="Image Cropper by FixTools"
  loading="lazy"
  allow="clipboard-write"
></iframe>

Attribution-friendly: a small "Powered by FixTools" link appears in the embed footer.

When pixel precision matters and why drag cropping is not enough

Many image destinations enforce strict pixel dimensions. Operating system app icons require exact sizes (16x16, 32x32, 64x64, 128x128, 256x256, 512x512, 1024x1024) and any deviation produces a fuzzy result because the OS applies its own resampling pass. Website CMS systems often have image cropping pipelines that work best when the source already matches the storage size, avoiding internal resampling. Email signature images need exact widths so they display consistently across email clients that do not respect CSS sizing. Print layouts at fixed DPI require exact pixel counts to produce the intended physical size on the page.

Drag-based cropping by eye lands close to the target but rarely exact. A few pixels off in either dimension is enough to trigger destination-side resampling, which adds artefacts and softens the result. The fix is to specify exact dimensions during the crop rather than after. FixTools accepts width and height as numeric inputs, locks the selection to those exact pixel values, and lets you drag the locked rectangle to choose the region. The export then produces a file with exactly the requested dimensions, verifiable by checking the file properties.

Pixel precision is particularly important for sets of images that must be uniform. A team page with 12 employee headshots looks designed when every photo is exactly 400x400. With each photo cropped freehand, the slight variations in dimensions translate into visible inconsistency in the grid layout. Using the pixel-precise mode means every photo can be cropped to exactly the same dimensions in a single session, with the locked rectangle repositioned over each new source image. The result is a uniform grid that reads as intentional rather than accidental.

For design contexts, exact pixel cropping enables tight layout integration. A web design with a 1920 by 800 hero banner expects exactly that size; a 1921 by 800 file gets scaled by the browser, introducing fractional pixel rendering that can blur sharp edges. A presentation slide with a 1280 by 720 background image expects exactly that size; a smaller or larger source either gets stretched or letterboxed. The cost of precision is one additional minute per crop to verify dimensions, and the benefit is integration with the destination layout without any artefacts.

Apple Human Interface Guidelines: App Icons Material Design: Image guidelines

How to use this tool

💡

Type the exact width and height into the cropper, drag the locked rectangle to position the subject, and export at pixel-precise dimensions.

How It Works

Step-by-step guide to crop image to precise pixels:

1
Load your source image
Drop the source photo into FixTools. The source resolution should be at least as large as the target export size, ideally larger to provide cropping headroom. A 4000-pixel source gives plenty of room to crop a 1280-pixel exact selection from any region.
2
Type exact width and height
In the dimension fields, type the exact pixel width and height you need. For example, 400 for width and 400 for height to produce a 400x400 square. The crop selection becomes a rectangle at exactly those pixel dimensions, locked to the entered size.
3
Drag to position the rectangle
The locked rectangle can be dragged anywhere over the source image. Position it over the subject you want to capture. Resize is disabled because the size is fixed by the typed values, but the rectangle is fully movable.
4
Verify dimensions before export
Confirm the width and height fields show the exact values you intend. If you accidentally typed an extra digit or transposed numbers, correct them before exporting. The crop selection updates live as you change the dimensions.
5
Export pixel-precise file
Click Crop. The exported file has exactly the dimensions you typed, verifiable by checking the file properties on download. There are no rounding errors and no off-by-one deviations. The file is ready for any destination that enforces strict pixel requirements.

Real-world examples

Common situations where this approach makes a real difference:

Designer producing app icon set

A designer produces an app icon set covering every OS-required size from 16x16 to 1024x1024. They crop each size from the master design at exactly the right pixel dimensions, producing nine files that line up with the OS icon spec exactly. The OS uses the appropriate file for each display context without resampling, producing crisp icons at every size where a single hand-cropped file would have softened on multiple sizes.

CMS administrator preparing hero images

A CMS administrator manages a website with a strict hero image size of 1920 by 800. They crop every new hero from photographer source files at exactly that size, uploading directly to the CMS without triggering the CMS's internal resampling. The site renders heroes at native resolution on every page, with no artefacts from upstream resampling. Page load is also faster because no client-side scaling is required.

Email marketer building newsletter assets

An email marketer builds a monthly newsletter with multiple inline images at specific widths. They crop each image to its exact required width (600 pixels for the main banner, 280 pixels for product thumbnails, 100 pixels for icons) so the email displays consistently across Gmail, Outlook, Apple Mail, and other clients. Email clients that ignore CSS image sizing still render the images at the source dimensions, which now match the intended layout.

Print designer matching DPI requirements

A print designer prepares photos for a printed booklet at 300 DPI. Each photo must be exactly 1500 by 1000 pixels to print at 5 by 3.33 inches on the page. They crop each source photo to exactly those pixel dimensions, ensuring the print rendering matches the layout grid without any in-pipeline resampling. The printed booklet shows photos at exact intended size with no visible artefacts.

Pro tips

Get better results with these expert suggestions:

Use higher-resolution sources for precise cropping

Pixel-precise cropping discards everything outside the selected region. The larger the source, the more flexibility you have to position the precise selection. A 4000-pixel source gives much more cropping headroom for a 1280-pixel target than a 2000-pixel source. Always work from the highest-resolution version available rather than starting from an already-cropped or already-scaled file.

Verify dimensions after export

Always check the exported file's dimensions before considering the crop complete. Open the file properties or use an image viewer that displays pixel dimensions. A 400x400 export should report exactly 400 by 400. Any deviation indicates either a tool issue or an unexpected change in the download pipeline. Verifying once per session catches issues before they propagate to production.

Keep the dimensions consistent across a set

For sets of images that must be uniform (team headshots, product thumbnails, gallery tiles), enter the exact dimensions once at the start of the session and the cropper retains them across multiple images. Each new source loads with the same locked rectangle ready to reposition. The result is a uniform set with verified pixel-perfect consistency.

Match destination DPI for print

For print destinations, calculate pixel dimensions from the intended print size and DPI. A 4-inch wide image at 300 DPI requires 1200 pixels. A 6-inch wide image at 300 DPI requires 1800 pixels. Web destinations typically use 72 to 96 DPI, so a 600-pixel-wide image renders at about 6 to 8 inches on a typical screen. Mismatching DPI produces either oversized or undersized print rendering.

FAQ

Frequently asked questions

Open the FixTools cropper, load your image, and type the exact width and height into the dimension fields. The crop selection becomes a rectangle at exactly those pixel dimensions. Drag the rectangle to position it over the subject you want to capture, then click Crop. The exported file will have exactly the requested pixel dimensions, verifiable by checking the file properties.

You cannot crop to a size larger than the source image because cropping discards pixels rather than creating them. If you need a result larger than the source, you would need to upscale (resize larger) rather than crop, and upscaling introduces artefacts because the tool has to invent pixels that were not in the source. The right answer is usually to use a higher-resolution source image when the target size is large.

In the FixTools cropper, type 400 into the width field and 400 into the height field. The selection locks to a 400x400 square. Drag the square over the subject and click Crop. The exported file is exactly 400 by 400 pixels. This size is common for profile pictures, avatars, and small thumbnails. For sharper retina rendering, consider exporting at 800x800 instead.

Yes. The dimension fields accept any pixel values, not just round numbers or standard sizes. Type 723 for width and 431 for height and the crop selection locks to those exact dimensions. This is useful for matching specific design grids, custom layouts, or unusual destination requirements that do not correspond to common preset sizes.

No. Cropping is a lossless operation that discards pixels outside the selected region. The kept pixels are bit-for-bit identical to the original. Quality loss only occurs from the export encoding, which is controlled separately by the format and quality settings. Export to PNG for lossless results or to JPEG at quality 95 or above for visually identical results with smaller file sizes.

Check the exported file's properties in your operating system file browser or in any image viewer that displays pixel dimensions. The reported size should exactly match the values you entered. FixTools enforces exact dimensions during export, so any deviation indicates an unexpected issue in the pipeline. A quick verification on the first export of a session confirms the workflow is working correctly.

Yes. The pixel dimensions you enter persist between images in the same session. After cropping the first image at, for example, 400x400, load the next image and the selection is already locked at the same size. Reposition the rectangle for each new source. The result is a set of images all at exactly the same dimensions, which is useful for grid layouts and uniform thumbnail sets.

No. The exported file contains only your cropped image at the exact requested dimensions with no FixTools branding, logo, or watermark. The clean export is true regardless of the size you requested or how often you use the tool. Pixel precision and watermark-free output are independent features and both are guaranteed on every export.

The maximum is limited by your source image size (you cannot crop to dimensions larger than the source) and by your device memory. Modern devices comfortably handle source images up to about 50 megapixels and crops up to about 8000x8000 pixels. For extremely large images such as gigapixel panoramas or scientific imagery, a desktop tool optimised for memory may be a better choice than browser-based cropping.