Image compression
Plenty of forms and share links stop at 1 MB, and a modern phone shoots four to twelve times that. Set 1 MB as the target, download a file that actually fits, and keep the photo on your device.
Open the Image CompressorPlenty of forms and share links stop at 1 MB, and a modern phone shoots four to twelve times that. Set 1 MB as the target, download a file that actually fits, and keep the photo on your device.
“Resize to 1 MB” and “compress to 1 MB” are the same job here, even though resize normally refers to pixels. A megabyte measures file weight, so what you are changing is how many bytes the picture occupies, not how wide it is. If the form asked for something like 1024×768 instead, that is a genuine resize — crop it in the Passport Photo Resizer first, then come back for the byte limit.
Check which megabyte the form means before you pick a number. 1 MB is 1024 KB when the validator counts in binary (1,048,576 bytes) and 1000 KB when it counts in decimal (1,000,000 bytes). Windows reports the binary figure, macOS reports the decimal one, and upload scripts split roughly down the middle. Aiming for 950–1000 KB clears both, which is why a file sitting at exactly 1024 KB is sometimes still rejected.
1 MB is a generous budget, so expect a light pass rather than a destructive crush. Most 4–12 MB phone JPEGs land under it at high quality with their full dimensions intact, and you should not be able to spot the difference on a monitor. Only very detailed RAW exports, stitched panoramas, and large PNG screenshots need a resolution cut as well.
Target-size mode searches for the highest JPEG or WebP quality that still fits, and only reduces resolution when quality alone cannot get there. Stay on JPEG unless the destination lists WebP. A photograph saved as PNG is the usual reason a 1 MB target fails outright — convert it to JPEG first, then run the target again.
1 MB is the wrong target for strict ID portals asking for 50 KB or 100 KB; use those pages instead. It is the right one when the upload allows it and you want the file to still look close to the original. Batch a whole folder before a share link so every transfer stays predictable. Nothing leaves your device.
Open Tokitool’s Image Compressor from this page, switch to target size, enter 1000 KB, and download once After reads under 1 MB. Despite the wording you are changing file weight, not pixel dimensions — at this budget the width and height usually stay exactly as they were.
1024 KB if the form counts in binary (1,048,576 bytes), or 1000 KB if it counts in decimal (1,000,000 bytes). You are rarely told which. Aim for 950–1000 KB and the file clears either one.
On this page, yes — both mean “get the file under a megabyte.” A true resize changes pixel dimensions, which is a separate job. If a form lists both a pixel size and a 1 MB cap, crop to the pixels first, then compress.
Yes, and usually without visible loss. Going from 10 MB down to 1 MB sounds drastic, but camera JPEGs carry a lot of detail your eye never registers, so target mode can find a quality that fits. Only start cutting resolution if the result still overshoots.
Roughly a 2000–3000 px wide JPEG at good quality: plenty for a full-screen view and fine for a 6×4 print. It is a fraction of a typical phone photo and about ten times a 100 KB form upload.
On screen, almost always. 1 MB is a light trim rather than a hard squeeze, so artefacts are rare on ordinary photos. Open the download at 100% zoom if the shot has large areas of smooth sky or gradient.
Use the tighter targets directly: Compress image to 500 KB, or Compress image to 100 KB for form and visa limits. Compress once from the original rather than re-compressing a file you already shrank, which stacks quality loss.
Use 1 MB when the portal allows it and you want maximum clarity. Drop to 200 KB or lower when an email limit or a strict form cap matters more than fine detail.
No. Compression runs in your browser through the same local path as the 100 KB and 500 KB pages. The photo never leaves your device.