A practical guide to your next decision
A practical field guide to image size, composition and file weight. Read from start to finish, or jump straight to the decision you need to make.
Worked example and sample files
Many camera JPEGs store pixels in one orientation and an EXIF instruction describing how to display them. A viewer that ignores that tag can show a sideways photograph. This editor asks its decoder to apply orientation once, calculates geometry from the oriented pixels and exports a new image without carrying the original EXIF tag forward.
Work through an example
Our asymmetric test image has red, green, blue and yellow corner markers. With EXIF orientation 6, a stored 120 × 80 source displays as 80 × 120. The exported pixels must keep that displayed orientation while removing the orientation metadata.
- Open the relevant tool below and choose a supported image. Check the original dimensions and bytes before changing anything.
- Set the dimensions and fitting mode for your destination. Enable enlargement only if you accept that it cannot restore missing detail.
- Process the image, switch between Original and Result, and check the final pixel dimensions and exact bytes. If a target is not met, change an allowed constraint and run again.
Check before you download
Check the downloaded file in another viewer when orientation matters. EXIF cleanup also removes GPS and other camera metadata; keep your original if you need those records. This is not a manual rotation or archival metadata tool.
Try the files yourself
The following original geometric illustration and exports are supplied with this project. These are actual files, not estimated savings. The exported examples use JPEG quality 85. Your own images will have different byte counts; compare details as well as weight.
| Result | Width × Height | File size |
|---|---|---|
| Original | 4032 × 3024 | 225354 bytes |
| Try a sample image | 1200 × 900 | 36438 bytes |
| Fit within bounds | 1440 × 1080 | 41113 bytes |
| Fill & crop | 1920 × 1080 | 44272 bytes |
| Add padding | 1920 × 1080 | 44602 bytes |
Choose your next step
Exported images remove EXIF, GPS and XMP metadata. Processing uses SDR/sRGB.
Normalize once, then inspect the saved pixels
An orientation problem can come from disagreement between stored pixels and the EXIF instruction used by a viewer. Applying rotation twice can be as wrong as ignoring it. This editor normalizes supported input before its geometry operations. Check the upright preview, then open the saved export in a separate viewer; the result should no longer rely on the original orientation metadata.
The tool does not provide arbitrary manual rotation as a dedicated editing workflow. If the image’s actual pixels were already saved sideways without a useful orientation tag, prepare a correctly rotated original elsewhere. Metadata removal also removes capture information from the delivery copy, so keep your archival original when dates or provenance matter.
Orientation and metadata are different from visible pixels
A phone photograph can store its orientation in an EXIF tag instead of physically arranging the pixel grid as you expect. Software that interprets the tag displays it upright; software that ignores it may show a rotated result. This editor normalizes the supported image’s orientation before processing and removes EXIF, GPS and XMP from the exported image. The goal is an upright pixel result that does not depend on retaining the original orientation tag.
Metadata removal is useful when preparing a shareable derivative, but it is not complete anonymization. A face, address, license plate or location visible in the photograph remains visible unless you change the composition yourself. Also preserve an archival original when dates, camera settings or authorship information matter to your workflow. The reduced export is a delivery copy, not an archival replacement.
What “processed on your device” actually means
Choosing a file gives this page a reference to the image in your browser session. Decoding, resizing and encoding happen on the device, and downloads are created from the resulting local data. The image editor does not upload the input, output or filename to a processing server. You do not need an account to use the tools. Clearing the editor releases its references; closing the page ends the session.
The website itself still requests pages, scripts and codecs from its static host. That is different from uploading your photograph. Optional ads and analytics are disabled in this installation. Local processing also does not control what happens after you save or share a file: your download folder, browser extensions, device backups and receiving applications have their own behavior. Review the privacy page for the boundaries of this service.
The download is the final test
A preview is helpful, but the saved output is what the receiving app will use. Check its actual dimensions, MIME type and exact bytes. Open the file in an image viewer, inspect the important details at a sensible scale, and confirm that transparency or the chosen background behaves as expected. If you created a ZIP, open it and compare its successful entries with the expected count.
When a result fails, change the constraint that is actually responsible. Wrong shape calls for a geometry decision; unreadable text calls for more detail or less aggressive encoding; excessive bytes call for a permitted compression or dimension change. Keep each candidate separate until you choose the final one. The original remains your reliable starting point for every new export.
- Check the real width and height, not only the requested box.
- Compare exact bytes with the destination’s ceiling.
- Inspect faces, lettering, product edges and transparent boundaries.
- Save the chosen output and keep the original separately.
The concepts behind this page
These relationships explain why changing one setting can affect another. Use them to identify which constraint matters most for your image.
- Image metadata
- Information such as EXIF orientation, camera details and GPS tags.
- Pixel dimensions
- The width and height of the decoded image grid.
- Local processing
- Image operations performed in browser memory on your device.
- File size in bytes
- The amount of data in the encoded download, measured after processing.
- Alpha channel
- Per-pixel opacity, including partially transparent edges.
- ZIP download
- One archive containing the successfully processed outputs.
- Local processing decodes images and removes exported Image metadata.
Questions worth asking before you export
Why is the output smaller than the dimensions I entered?
Fit treats both dimensions as maximum bounds and preserves the original ratio. It can therefore produce a smaller rectangle. Use padding for an exact canvas with the complete image, or cover when you accept removing edges.
Does quality 100 make the export lossless?
No. JPEG quality 100 is still an encoding setting, not a promise of identical source pixels. Resizing itself also changes the grid. Preserve the original when you need an unchanged archive.
Can enlargement recover missing text or faces?
No. Enlargement estimates new pixels and cannot reliably reconstruct details absent from the source. Find a higher-resolution original when those details are important.
Sources and how to verify the examples
The numerical examples on this page come from explicit geometry calculations and the project’s synthetic files. Hypothetical byte counts illustrate acceptance rules; downloadable sample counts describe those specific files. The references below explain the underlying formats and browser export API, not a guaranteed saving or acceptance by another service.
Ready to prepare your image?
Keep the original, choose one clear requirement, and inspect the exported file. A useful result meets its destination’s rules and keeps the details that matter.
Back to the image tools