Drop images here or JPG · PNG · WebP · GIF · AVIF · BMP · HEIC
Results
Figures measured October 2026 with the engine that runs this tool.
Kept under 200 KB, our 12-megapixel phone photos came back between 1,564 and 2,550 pixels wide as JPEG, and a studio portrait on a plain background kept every one of the 2000 × 3000 pixels that reached the server. The tool below starts at 195 KB, which is 199,680 bytes: under 200 KB whichever way the form counts a kilobyte, 1,000 bytes or 1,024. Switch the format to WebP first if you're compressing screenshots.
| Input | Pixels out | Bytes | Notes |
|---|---|---|---|
| Headshot | 2000×3000 | 198,667 | Quality 72; not resized |
| Phone: bus | 2550×1913 | 199,496 | Quality 30 |
| Street, JPEG | 1564×1173 | 197,592 | Quality 36 |
| Street, WebP | 1329×997 | 199,508 | Quality 36 |
| Flowers, JPEG | 1564×880 | 198,260 | Quality 39 |
| Flowers, WebP | 1329×748 | 198,454 | Quality 45 |
| HEIC: car | 2184×2912 | 197,526 | Quality 30; about 6 s |
| HEIC: dogs | 1577×2103 | 196,645 | Quality 34; about 5 s |
| Screenshot, WebP | 2448×1530 | 198,976 | Quality 44 |
| Screenshot, JPEG | 2080×1300 | 197,347 | Quality 37 |
| Screenshot, PNG | 986×616 | 144,613 | 72% of the target |
| Random noise | 1252×835 | 199,286 | Quality 33 |
A row that doesn't name a format is JPEG. Every phone photo went in straight off the camera at 12 megapixels: the bus and street at 4032 × 3024 and the flowers at 4032 × 2268 from a Google Pixel 4a, the car and the dogs as 3024 × 4032 HEIC files from an iPhone 12 Pro. The portrait started as a 3413 × 5120 studio shot, the screenshot is a 1440 × 900 browser window captured at 2× pixel density (2880 × 1800), and the noise image is 2400 × 1600. Times come from a fast desktop machine; the live server is slower. These numbers come from running the engine directly; when we put the same files through this page in Chrome, eleven of the twelve came back at the same pixel size within a quality point or two. The exception was the flower photo as WebP, which kept 1564 × 880 at quality 30, because the browser's own first resize hands the search a slightly different file.
On text and flat interface colours, WebP pulled clearly ahead in our test. It kept the screenshot at 2448 × 1530, where JPEG managed 2080 × 1300. PNG, often recommended for screenshots, did worst: it had to drop to 986 × 616, and because PNG can only resize in coarse steps, it finished at 144,613 bytes, well short of the budget. A lossless PNG is still the format for a screenshot that must stay pixel-exact, but this tool's size search trims a PNG's colours to make it fit, so when the job is getting under a limit, WebP keeps more of the picture.
The usual advice is that WebP beats JPEG at the same file size. For our two phone photos at the same 195 KB target, WebP never came out wider than JPEG. In the engine test both were narrower, 1,329 pixels against 1,564; run through this page in Chrome, the flower photo matched JPEG's 1,564 and the street photo was still narrower. That doesn't make WebP the worse format. The search lowers each format's quality to a floor of about 30 before shrinking, and 30 doesn't mean the same thing in both, so the comparison isn't like for like. The practical upshot: don't switch a photo to WebP expecting a bigger picture at this size. Pick the format the destination asks for. The format guide covers the rest.
Before uploading, the page shrinks any JPEG, PNG or WebP larger than 3,000 pixels on its long side down to 3,000, right in your browser. That's why the 3413 × 5120 headshot shows up as 2000 × 3000: under 200 KB, the search never needed to shrink it further. HEIC files skip that step because most browsers can't decode them, so the server compresses the full image, which is why the two iPhone photos took about 5 to 6 seconds against 2 to 3 for most of the JPEGs.
NTA's NEET (UG) 2026 information bulletin accepted the candidate's photograph as a JPG of 10 KB to 200 KB. For finger and thumb impressions it contradicts itself: page 16 says 10 KB to 200 KB, page 17 says 50 KB to 300 KB. When a notice disagrees with itself, aim for the overlap both readings accept, 50 to 200 KB in this case; the 195 KB preset sits inside it.
The bulletin doesn't say whether its kilobyte is 1,000 or 1,024 bytes, and almost no form does. This tool counts 1,024, and when we ran the files above at a straight 200 KB, nine of the twelve landed between 200,001 and 204,800 bytes. At the 195 KB preset every one of them stayed under 200,000. Next year's bulletin may move these numbers, so check it before you upload.
Tighter limits work differently. At 100 KB, documents still hold up well; at 50 KB a full phone photo drops below 1,000 pixels wide, which is why cropping first matters there.
It is a reasonable budget for a large photo, not a rule; there is no official per-image limit for web pages. At the 195 KB preset our 12-megapixel test photos kept 1,564 to 2,550 pixels of width as JPEG. Whether that is enough depends on how wide your page shows the image. For thumbnails, aim much lower.
For screenshots, WebP: it kept a 2880 × 1800 screenshot at 2448 × 1530, against 2080 × 1300 as JPEG. For photos it depends; on our two phone photos WebP never came out wider than JPEG at the same target, and sometimes narrower (1,329 against 1,564 pixels). If a form or site asks for JPG, use JPG.
PNG has no quality setting to fine-tune, so the search can only change its size in fairly big steps: each step cuts the width by about 30%. Our screenshot came out at 144,613 bytes, 72% of the 195 KB target, because the next size up did not fit. JPEG and WebP land much closer to the target.
Yes. Drop a batch in and each file is compressed to the same target and format separately; you can download them one by one or as a single ZIP. The per-file size limit is shown in the drop zone, and you are told if a batch has more files than the server takes at once.
The page shrinks large JPEG, PNG and WebP files to 3,000 pixels on the long side in your browser before uploading them, but most browsers cannot decode HEIC, so the server has to work through the whole 12-megapixel original. At the 195 KB preset our two iPhone HEIC files took about 5 and 6 seconds on a fast desktop machine, against 2 to 3 seconds for most JPEGs.
No account, no watermark, and no copy of your image is kept: uploads are deleted as soon as they're compressed. The privacy policy describes the metadata-only log in full, and the quality guide explains why the search gives up pixels before it gives up quality below 30.