Why pixel size and KB limit both matter
Passport, visa, exam and signature uploads almost always state two separate requirements: exact pixel dimensions (so the photo prints or displays correctly) and a maximum file size in KB (so their system accepts the upload). Hitting only one isn't enough - resize to the wrong file size and a portal will reject it even if the dimensions are perfect. This tool does both in one pass: crop, resize to the exact pixels, then compress down to the size cap.
How the processing actually works
After you drag the crop box to frame your shot, the tool extracts exactly that region and resizes it to your target width and height. It then encodes the result as a JPEG starting at a high quality setting, using mozjpeg, a modern, efficient encoder, and steps the quality down gradually until the file fits under your KB limit. This means you always get the sharpest possible result that still satisfies your size requirement, rather than a fixed, one-size-fits-all compression level applied regardless of how much room your limit actually allows.
Why your crop choice matters so much
Since the tool resizes your crop box directly to the target pixel dimensions, it's worth dragging the crop to roughly match the aspect ratio of the dimensions you're targeting - a crop with very different proportions than the target size gets stretched to fit, which can visibly distort the photo. Taking a moment to frame the crop proportionally before resizing produces a far more natural-looking result than letting the tool stretch a mismatched shape into place.
Always double-check against your actual form
The presets here reflect commonly published, typical requirements - but passport offices, embassies and exam boards do change their specs, and some ask for things a generic tool can't verify (a plain white background, no smiling, no glasses). Use "Custom" if your form states different numbers, and treat any preset as a strong starting point, not an official guarantee.
Getting a plain background
This tool crops, resizes and compresses, but it doesn't replace or clean up the background behind you - if your form specifically requires a plain white or light background and your photo was taken against something else, running it through our Remove Background tool first, then uploading the result here, gives you a properly plain background before the sizing and compression steps run.
Signatures
For a signature, sign in dark ink on plain white paper, photograph it in even light, then crop tightly before picking the signature preset (or custom dimensions) - a clean, high-contrast source compresses much smaller than a shadowy phone photo, since there's less uneven background noise competing for your limited size budget.
Who actually needs this, and why
Travelers applying for a passport or visa where the application portal specifies exact photo dimensions and a file size cap. Students and job applicants submitting a photo or signature to an exam registration or recruitment form with similarly strict, dual requirements. Anyone who has tried uploading a standard phone photo only to have it rejected for being the wrong pixel size, too large in file size, or both at once.
Why compression lands a little under your limit, not exactly at it
Compression works by lowering JPEG quality in discrete steps rather than continuously, which means the result typically lands a little under your stated KB limit rather than landing exactly on it - this is normal, expected behavior and still satisfies any form that states a maximum size, since being under the cap is what actually matters for a successful submission.
Privacy
Your photo is processed on our servers over an encrypted connection, and both the uploaded photo and the result are removed automatically after a short period. There's no account required and no watermark added to the result.
What happens if the file still can't reach your limit
Occasionally, especially with a very tight KB limit, even the lowest usable quality setting can't quite fit under your target - in that case, the practical fix is cropping in tighter rather than looking for a different compression option, since a smaller crop at the same pixel dimensions has less fine detail to encode and compresses more efficiently as a result. This is a genuinely more effective solution than hoping a stronger setting exists somewhere, since the tool already searches the full usable quality range on its own.
Reusing a photo across several applications
Since different forms often specify different exact dimensions and KB limits for what's fundamentally the same photo, it's worth keeping your original, uncropped photo saved separately so you can run it through this tool again with different settings each time a new application comes up - starting fresh from the original each time produces a cleaner result than resizing and compressing an already-processed file a second time, which tends to compound quality loss across repeated rounds of editing.
Taking a photo that works well from the start
A well-lit photo with even lighting across the face, a plain background, and the subject facing the camera directly gives this entire process much better material to work with than a dim, shadowy, or oddly-angled photo would. Starting from a clean source photo matters more the tighter your specific form's KB limit happens to be, since there's less room for a poor original to be compensated for during compression.
Checking your result before submitting
Before uploading to the actual form, open your processed photo once and compare its reported pixel dimensions and file size against the numbers printed in the form's own instructions - small mismatches, like mixing up width and height or missing a unit difference, are easy to make and are a common reason a correctly-processed photo still gets rejected on submission even though the crop, resize and compression steps handled on our end all completed perfectly fine throughout the entire process. This simple comparison, done once before you submit, catches far more real submission problems than any amount of careful compression ever could on its own.