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
Distinguish decode failures, over-target results and larger files, and understand local processing.
Select up to eight JPEG, PNG or WebP still images. Limits are 12 MiB per file, 48 MiB per batch and 24 million pixels per image. A MiB is 1,048,576 bytes and differs from the decimal KB target. Renaming an extension to .jpg does not convert the underlying file.
HEIC and GIF inputs are not accepted. Animated PNG or WebP may become a still image. Preserve animation or multi-page documents with an editor that supports their original structure.
If decoding fails, check whether another image viewer can open the original. If it can, export a supported JPEG or PNG and try again. The extension alone cannot prove a file is valid.
If the browser runs out of memory or stalls, process one image at a time, close other large tasks or reduce dimensions in the original editor. A small compressed file can still require substantial decoded pixel memory. Save needed results before refreshing, because a refresh clears the current work.
Re-encoding an already optimized file may make it larger. This tool checks a byte target but does not guarantee a smaller file than the original. Use the change indicator; if the original already meets the destination’s requirements, it may be the better choice.
Over target does not mean the file is corrupt. It means the selected dimensions, format and byte limit could not all be met. Allow further resizing if acceptable; otherwise reconsider the permitted format or byte limit to keep small text readable.
Selected files are decoded, drawn to a canvas and encoded inside the current browser. The converter code does not upload images. Preview URLs are temporary browser object URLs, not public sharing links. Closing the page or clearing the selection releases the tool’s file and result references.
Re-encoding does not guarantee preservation of EXIF, location or color profiles. It also is not a certification that every sensitive detail was removed. Inspect both the resulting pixels and metadata before sharing sensitive images.
The hosting and analytics services may receive page access information when the site loads. This is separate from uploading images for processing. The privacy page describes analytics and the current advertising state. Results are not archived for you; download any files you want to retain.
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.