A practical workflow for file size limits
Separate bytes from pixels and decide what to change when a submission fails.
Written and maintained by Anti forge · Updated September 24, 2026
Choose a format for photos, text screenshots or transparent artwork, then compare with the same sample.
The smallest file is not always the best choice. A WebP cannot satisfy a JPEG-only submission even when it is smaller. For web publishing, check format support in the target browser and publishing tool. Keep the original separately and inspect the displayed image after uploading.
| Format | Behavior in this tool | What to inspect |
|---|---|---|
| JPEG | Adjustable quality; transparent areas flattened onto white | Artifacts around small text |
| PNG | No quality-based size reduction; may resize | Dimensions after fitting the target |
| WebP | Adjustable quality with alpha support | Target support and edge quality |
The checkerboard behind a preview is a display background, not pixels added to the file. The transparency sample contains an opaque blue circle and a translucent orange rectangle. With PNG or WebP, inspect the outer area and overlapping shapes. JPEG intentionally replaces transparent areas with white in this tool.
Converting a JPEG with a white background into PNG does not restore transparency: the white background is already part of the pixels. Background removal is a separate editing operation and is not performed by this converter.
PNG encoding does not use the JPEG quality slider to fit a target. This tool reduces dimensions when a PNG exceeds the limit. A lossless file format cannot preserve details removed by resizing. Enable the option to keep dimensions for text screenshots and inspect any over-target status.
Load the samples, keep the byte target and maximum edge constant, then save JPEG, PNG and WebP in turn. Record bytes and dimensions and open previews at their natural size. Small thumbnails can hide compression artifacts.
Browser encoders may produce different sizes or visual results. This guide does not promise a fixed saving percentage. The numbers on each result card describe the actual file generated by your current browser.
The workflow above describes Pixel Workroom. These primary references explain general browser APIs and image formats.
Separate bytes from pixels and decide what to change when a submission fails.
Choose a format for photos, text screenshots or transparent artwork, then compare with the same sample.
Use worked examples to understand the maximum edge, aspect ratio and further resizing.
Distinguish decode failures, over-target results and larger files, and understand local processing.