Flagship workflow

Build images that meet an upload form’s rules

Instead of guessing why a form rejects an image, check the file and prepare it for a maximum size, required format, and dimension rule. Prepared copies are EXIF-oriented and rewritten without EXIF/GPS metadata.

Output formatMaximum file size

Dimension behaviorWidth (optional)Height (optional)Transparent-area backgroundRebuild files that already pass as metadata-clean copies. If unchecked, compliant files remain available unchanged.

Add up to 20 images for a local preflight

Signatures, size, dimensions, aspect ratio, transparency, and detectable metadata are checked before preparation.

Uses PixelConvert’s copyright-safe 1200×630 sharp-text test PNG and follows the same preflight and preparation path as your files.

Preflight first

The browser checks the actual signature, byte size, available dimensions, aspect ratio, transparency, and detectable metadata categories. Browser-unsupported HEIC/TIFF details are confirmed by the server during preparation.

A real size ceiling

JPEG and WebP use a bounded quality search. PNG stays lossless and may reduce dimensions in fit mode. The endpoint rejects impossible fixed-dimension requests instead of returning an oversized file.

Privacy by construction

Preparation uses in-memory buffers. Outputs are re-encoded without EXIF/GPS data, and completed batches reuse the server-generated ZIP flow.

Tested behavior and browser limits

Last tested: 2 September 2026
Responsive checks: Current Chromium desktop and 390 px mobile viewport
Local preview: JPEG, PNG and WebP where the browser decoder supports them
Server confirmation: HEIC/TIFF details, output feasibility and final metadata policy

Client inspection is informative rather than forensic. Preparation uses the production API, and impossible fixed-dimension requests return an explanation instead of an oversized file.