How to Reduce Image Size in KB for Forms, Portals and Email

A phone camera saves a photo at 12 megapixels or more, which usually means 2–5 MB per picture. An application portal that collects a photo and a signature from hundreds of thousands of people would need terabytes of storage if it accepted those files as they are, and every reviewer would wait for them to load. A cap in kilobytes is the simplest rule a developer can enforce: the server reads the byte count before it even opens the image, and rejects anything larger. That is why the error message talks about KB and not about how the picture looks.

The numbers vary widely, and most are far below what a camera produces. The US State Department asks for a digital visa photo of 600 × 600 to 1200 × 1200 px and no more than 240 KB (the rules are on travel.state.gov). Indian recruitment portals such as IBPS have asked for a signature of 10–20 KB and a photograph of 20–50 KB. University admission systems, rental platforms and HR software often settle on 100 KB, 200 KB or 1 MB. Email is more generous, with Gmail allowing 25 MB of attachments per message, but a dozen full-size photos still blow past it.

Some forms check more than the byte count. A portal may also demand exact pixel dimensions, a JPG or JPEG extension, or a minimum size so the picture is not a postage stamp. Read the notice once, note all three numbers (KB, pixels, format) and work toward all of them at the same time. Getting the KB right while ignoring the pixel rule only earns you a different rejection message.

Pixel dimensions are the biggest lever by far. File size grows with the number of pixels, and the number of pixels grows with the square of the width: halve both the width and the height and you keep only a quarter of the pixels. Taking a 4032 × 3024 photo down to 1600 × 1200 throws away about 84% of the pixels, and the file typically shrinks by a similar share before you touch quality at all. For anything shown on a screen or checked by a human reviewer, 1200–1600 px on the long side is plenty. Cropping counts here too: every pixel of empty wall you cut is a pixel the encoder no longer has to store.

Format decides how efficiently those pixels are packed. JPG was standardized as ISO/IEC 10918-1 in 1992 and is built for photographs: it discards fine detail the eye barely notices. PNG is lossless, which is perfect for logos and screenshots and wasteful for photos, so the same snapshot as a PNG is often several times the size of the JPG. WebP and AVIF are smaller still at similar quality, but many government and recruitment portals accept only JPG or JPEG, so they are the right choice for websites and chat apps rather than forms. If you are unsure which format a form means by "JPEG", the guide to JPG, JPEG and PNG clears it up.

Quality is the fine-tuning knob and works only on lossy formats. Most cameras and phones save JPGs at quality 90 or higher, and dropping to 75 typically halves the file with no difference you can see at normal viewing size. Below about 50, smooth areas such as sky and skin start to break into blocks and text gets halos. That is why quality should come last: on a full-size photo it has to be pushed so low to reach a small target that the damage shows, while on a resized photo a gentle reduction is enough. Removing metadata (GPS position, camera model, embedded preview) is a free bonus worth 10–50 KB on many phone photos.

JPG has no setting that says "make this 50 KB". A given quality value produces a different size for every photo, because a busy picture of leaves needs more bytes than a plain wall. Desktop editors solve this by trial: export, look at the size, adjust, export again. It works, but it takes several rounds, and it is easy to overshoot and end up with a 30 KB file that looks rough when 49 KB would have looked clean. The method below keeps the guessing short by fixing the pixel size first, so quality only has to cover the last stretch.

A size-targeting compressor does the same search for you. In the image compressor, keep Compress by on Target size, type the number and pick KB. The tool tries quality values until it finds the highest one that fits, and, with Allow downscaling on, reduces the dimensions in small steps if quality alone stops at the Lowest quality allowed. For the most common limits there are pages with the number already filled in: compress an image to 20 KB for signatures and exam photos, and compress an image to 100 KB for job portals and visa forms. If you would rather set the strength yourself, Quality level and Percentage are the manual modes under the same switch.

Here is how a typical 3.2 MB phone photo moves toward a 100 KB limit when the levers are applied in order. The figures are typical, not measured, and a detailed scene will land a little higher.

Phones offer a few built-in shortcuts, but none of them let you type a KB number. On an iPhone, Mail asks whether to send a photo at Small, Medium, Large or Actual Size when you attach pictures, and the Shortcuts app has Resize Image and Convert Image actions. Since iOS 11, iPhones save photos as HEIC by default (Settings, Camera, Formats, High Efficiency), and many portals refuse HEIC, so converting to JPG is part of the job. On Android, galleries differ by maker: Samsung's Gallery editor includes a resize option, while Google Photos is built for editing rather than for setting a pixel size. A browser-based tool sidesteps the differences because it works the same on every phone.

On a computer you have more control. On a Mac, Preview resizes under Tools, Adjust Size, and its File, Export dialog shows a Quality slider for JPEG along with an estimate of the resulting file size, which makes manual targeting quicker. On Windows, the Photos app can resize an image from its menu, and Paint offers Resize with percentage or pixel values before you save as JPEG. Both platforms leave the final KB number to trial and error, which is fine for a single file and tedious for twenty. For batches, a browser tool with a size target handles up to 20 images in one go, 95 MB each, with nothing to install.

Taking a screenshot of a photo is the most common workaround, and it sometimes produces a smaller file by accident. The catch is that you have no control over what you get: the screenshot captures the screen's resolution, not the photo's, adds whatever bars and borders were visible, and on most phones is saved as PNG, which is the wrong format for a photograph. On a modern phone a full-screen PNG screenshot can easily weigh more than the JPG it shows. Cropping it afterwards, then converting, then compressing takes longer than compressing the original once.

Renaming a file is the other trap. Changing photo.png to photo.jpg, or photo.heic to photo.jpg, changes only the label: the data inside is still PNG or HEIC, the size is identical, and portals that read the file header reject it or fail to display it. Zipping does not help either, because JPG data is already compressed and a ZIP of a JPG is about the same size. Forms also want an image, not an archive, so a ZIP is refused outright.

PNG became a W3C Recommendation in 1996 as a lossless format, and lossless means it may not throw away any detail to save space. It packs repeated patterns efficiently, which is why a screenshot of a document or a logo on a flat background compresses well. A photograph has almost no exact repetition, since every pixel differs slightly from its neighbors, so a PNG photo stays large no matter how carefully it is optimized. If a 1200 px PNG photo is 1.8 MB, lossless optimization might take it to 1.6 MB; saving the same pixels as JPG at quality 75 typically gives 150–250 KB.

There are two honest ways out. If the image is a photo and the form accepts JPG, change the Output format to JPG and the size problem mostly disappears; transparent areas are filled with a solid color, which forms rarely mind. If it must stay PNG (some signature uploads and design portals insist on it), switch PNG compression to lossy, which reduces the image to the colors it actually uses. A signature in dark ink on white needs only a handful of shades and drops dramatically, while a colorful photo loses visible smoothness in gradients.

When neither helps, the remaining lever is pixels again. A transparent product cut-out at 3000 px cannot be both PNG and 50 KB without becoming smaller; 800 px might fit. Check whether the form really needs the transparency, because a white background in JPG is often accepted and is a fraction of the size.