Resize and Compress Images for Web Forms
For anyone uploading evidence to an insurance claim, photos to a rental application, attachments to a council form or images to a marketplace listing, and hitting a wall of rejection messages. There is a fixed order of operations that works, and once you know it the job takes a minute.
ZillaKit team · Published September 2026
A phone camera produces files sized for printing at A3. A web form usually wants something suitable for a thumbnail. The mismatch is enormous, and the form typically tells you only that your file was too big, with no advice on what to do about it. Here is the reliable sequence.
Read the limit properly before you start
Forms impose up to four separate constraints, and people usually only notice one.
- File size, stated in kilobytes or megabytes. The most common.
- Pixel dimensions, either a maximum, a minimum, or an exact requirement. Minimums exist because the organisation needs enough detail to read a document or see damage in a photo.
- File format. Usually JPEG and PNG accepted, often PDF as well, and frequently nothing else.
- Aspect ratio, occasionally, typically for profile images that must be square.
Write all four down before touching the image. Half the frustration in this task comes from fixing one constraint and breaking another, then going in circles.
The order of operations
Format first, then dimensions, then quality. Doing it in any other order wastes effort.
Step one: get into an accepted format
If your photo came off a recent iPhone it is probably a HEIC file. Apple adopted this format because it stores an image at similar visual quality in roughly half the space of a comparable JPEG. That is a genuine improvement, and it is also why so many upload forms reject it: HEIC support outside Apple's ecosystem is still patchy, and a lot of government and corporate systems were built before it existed.
Convert to JPEG with HEIC to JPG and the problem disappears. Expect the JPEG to be larger than the HEIC was, since you are moving to a less efficient format, so budget for that when you get to the size step. You can also stop the problem at source: in the iPhone camera settings, switching the capture format to the most compatible option makes the phone record JPEG directly, at the cost of larger files on the device.
If you have a PNG photograph, convert it to JPEG too. PNG is lossless and excellent for screenshots, logos and anything with flat colour or transparency, but it is a poor choice for a photograph and produces files several times larger than necessary.
Step two: set the dimensions
This is the step that does most of the work, and skipping it is the main reason people end up with a horrible looking image. File size scales roughly with the number of pixels, and pixel count scales with the square of the dimensions. Halving both the width and the height removes about three quarters of the pixels.
Ask what the image is actually for. A photo that will be viewed on a screen in a claims system does not need to be 4000 pixels wide, because nobody will ever display it at that size. Sensible targets:
- Around 1000 to 1600 pixels on the long edge for a general photograph that someone will look at on a monitor.
- Around 2000 pixels on the long edge if fine detail matters, such as a photo of a document or a serial number.
- Whatever the form specifies, exactly, if it specifies anything.
Use Resize Image and keep the aspect ratio locked unless the form demands a specific shape. Very often the resize alone brings you under the limit and you can stop here.
Step three: compress to the target
If you are still over, now reduce JPEG quality. The relationship is not linear: moving from the maximum setting down to around three quarters typically cuts the file dramatically while producing a difference most people cannot see. Pushing much below half starts producing visible blocking, particularly across smooth gradients such as sky or a painted wall.
Rather than guessing and re-exporting repeatedly, use Compress Image to KB and state the number you need. It adjusts the compression until the output lands under your figure, which turns a trial and error loop into one operation. If the form gives a range, aim below the midpoint rather than just under the ceiling, because some systems re-encode on receipt and the size can move.
A worked example
You need to upload six photos of storm damage to an insurance claim. The portal accepts JPEG and PNG, maximum 2 megabytes each, minimum 800 pixels on the shortest side.
- The photos are HEIC from a phone. Convert all six to JPEG first.
- Originals are around 4000 by 3000. Resize the long edge to 1600, which puts the short edge at 1200, comfortably above the 800 minimum.
- Check the sizes. At 1600 pixels they are likely well under 2 megabytes already, so no compression step is needed.
- Before uploading, consider the location data. Photos carry embedded metadata including where they were taken. For an insurance claim on your own property that is usually harmless or even helpful. For a marketplace listing showing an item inside your home, it is not. Check or strip it with EXIF Viewer and Remover.
- Rename the files so the assessor can follow them: roof-north, fence-rear, and so on. It costs a minute and materially improves how your claim reads.
Working through a batch
When you have twenty images rather than one, pick a single target and apply it to everything rather than optimising each file. Consistency also looks more professional to whoever receives them. Resize everything to the same long edge, convert everything to the same format, and only handle exceptions individually.
Keep the originals. Always. Resizing and compressing are destructive, and a JPEG that has been compressed, saved, opened and compressed again accumulates damage that cannot be undone. Work from a copy, and if the result is wrong, start again from the original rather than from the processed file.
Honest limits
You cannot have a small file and full detail at the same time. If a form demands a photo under 100 kilobytes and also wants readable small print on a document, those requirements are in tension, and the answer is usually to crop tightly to the relevant portion rather than to shrink the whole page. A cropped close up of one paragraph at moderate quality beats a full page at terrible quality every time.
Some portals are also simply badly built. They will reject a valid file with a generic error, or impose an undocumented limit. If a compliant file keeps failing, try a different browser, try a smaller file than the stated limit, and check whether the filename contains spaces or unusual characters, which occasionally breaks older systems.
Finally, note that every step here can be done on your own device without a photograph of your damaged home, your children or your identity documents being sent to a processing server. For this category of image that is worth a moment's thought before choosing a tool.
Tools mentioned
- Resize Image – Set pixel dimensions, which is the first and biggest lever.
- Compress Image to KB – Target an exact kilobyte figure instead of guessing at quality.
- HEIC to JPG – Convert iPhone photos into a format upload forms accept.
- Image Converter – Move between JPEG, PNG and WebP.
- EXIF Viewer and Remover – Inspect or strip location and camera data before sending a photo out.
Related guides
- Remove a Photo Background in Your Browser – When the upload also needs a clean subject on a plain background.
- Compress Photos for Online Forms – The identity photo case, with millimetre sizing and head position rules.