Prepare Images for Upload Forms: Pixels, Format and KB

Write down the actual requirements

Read the form’s current instructions rather than following a universal upload recipe. Record allowed formats, width and height rules, maximum bytes, whether transparent backgrounds are accepted, and any content or framing instructions. A demand for 100×100 pixels is not interchangeable with a 100KB limit. FileOnTap does not certify passport photos, official documents or a named service’s acceptance; those may have requirements beyond image geometry and bytes.

Start with a clean original and the right orientation

Keep a backup and choose a static JPG, PNG or WebP source. Current browsers apply supported JPEG EXIF orientation when decoding; verify the preview and output rather than assuming older software behaves identically. Remove irrelevant margins in a source editor when framing matters. HEIC sources need conversion first. A screenshot of a photo can discard detail and add interface decorations, so prefer the actual source file when available.

Establish the required canvas

Use crop for an exact canvas that is filled, or pad for an exact canvas that retains the whole source. Fit is appropriate for maximum bounds but may output a smaller side. Avoid stretch unless distortion is acceptable. Choose PNG or WebP to preserve transparency, or select a solid background for JPG. The local resizer reports actual pixels after each output; different source aspect ratios are handled independently even when the batch shares settings.

Apply a byte budget and recheck the pixels

Use the compressor on a saved resized copy when the form also limits KB. Select decimal KB or binary KiB deliberately. Check each reached/not-reached status, then open the result and verify its pixels again because target compression can reduce dimensions. An already-fitting original stays unchanged; re-encoding is not allowed to make the file larger. If all constraints cannot be satisfied together without unacceptable detail loss, prepare a better source or ask the receiving service for guidance.

Save, inspect and submit deliberately

Use per-file downloads when only some outputs are suitable. ZIP contains successful results and is capped at 100MiB; it does not make an image comply with a form that expects an individual file. Local processing does not upload your image to FileOnTap, though page assets and consented analytics can use the network. Once downloaded, the file’s destination is under your control. On a memory-limited phone, use fewer files or a smaller output canvas rather than retrying a large batch endlessly.

Further reading

Browser image export and file-size units: MDN canvas toBlob and NIST SI prefixes. These describe APIs and units, not a guarantee of any upload service accepting your file.