CLEAR BOUNDARIES
Your images stay with you.
Postbatch processes selected images inside your browser. Here is what local processing protects, what an export still contains, and where the tool's practical limits apply.
What happens to your files
The editor reads files you select and performs framing, resizing, conversion, compression, watermarking, and ZIP creation locally. It does not upload source images, logo files, or generated exports to an image-processing service. Original files are read without being overwritten.
The batch is held for the current page session. Postbatch does not save images or recipes to browser storage. Reloading or closing the tab clears the editor's batch; files you already downloaded remain in your chosen download location. Your browser and operating system still manage memory, caching, history, and downloads.
Page requests still reach the host
Opening Postbatch loads its HTML, styles, scripts, and bundled library from the site's host. Normal page requests may include your IP address, browser information, and the requested URL. Hosting infrastructure may keep operational logs under its own policies.
Postbatch includes no advertising trackers or analytics scripts. The editor does not require an account or a paid API. This public tool is served by its hosting environment; that is separate from local image processing. If you follow a documentation link, the destination website handles that visit under its own privacy terms.
EXIF removal is not anonymization
Each output is rendered into a new pixel image and encoded again. The original EXIF metadata, including an embedded GPS location, is not copied into the exported image. Orientation is applied to the pixels before encoding, so supported rotated originals remain correctly oriented.
Visible information remains visible. A face, a street sign, an address on a package, identifying text, or a recognizable location is still part of the image. Added watermarks may identify you as well. Postbatch does not blur, redact, or anonymize those details.
The ZIP export report includes original filenames and output information. Output names may also retain information from the original name. Review filenames, pictures, and the report before you share them. Keep originals securely if you need their metadata for another purpose.
File, pixel, and memory limits
| Images in one batch | 20 |
|---|---|
| Each source file | 20 MB |
| Combined source files | 100 MB per batch |
| Source image dimensions | 12 million pixels; at most 16,384 px on either side |
| Output image dimensions | 6 million pixels; at most 8,192 px on either side |
| Combined output images | 60 MB per ZIP, before its small report and archive overhead |
| Logo upload | 5 MB and 4 million pixels |
The file limits use 1 MB = 1,048,576 bytes; target-size controls use 1 KB = 1,024 bytes. Files are processed sequentially to limit memory use. These ceilings cannot guarantee that every device has enough free memory. A small compressed file can still occupy much more memory when decoded.
If a device struggles, reduce the number of images or their dimensions. Cancel stops the batch at a safe processing boundary; a browser decode or encode already underway may finish before cancellation takes effect. The originals remain available for another attempt.
Supported formats and export tradeoffs
Input supports JPG, PNG, and still WebP. The editor checks file signatures and dimensions before decoding. HEIC, SVG, GIF, animated PNG, animated WebP, and damaged or unsupported encodings are rejected. A filename extension alone does not establish that a file is valid.
JPG has no transparency, so transparent originals require confirmation of the flattening background. Crop can retain transparency in PNG and WebP. Adding borders uses an opaque background. PNG is lossless and ignores the quality slider; JPG and WebP target searches lower quality without silently reducing dimensions.
A target file size may be impossible at the selected dimensions. The result then reports the actual size and an unmet target. Browser encoders and color management may produce different results, so inspect the processed preview and numbers before downloading. The batch guide explains the target-size controls.
Use your own content and inspect the result
Only process images and logos you own or have permission to use. A watermark does not prove ownership or stop someone from copying an image. The built-in sample images are synthetic artwork created for this tool and contain no private account material.
Postbatch prepares files. It does not publish to social accounts, verify a platform's current upload requirements, or guarantee that a destination will accept an export. The available ratios and pixel settings are general choices.
Browser references
For the underlying browser features, see MDN's canvas image export documentation and MDN's image bitmap and orientation documentation. These references describe browser APIs; the limits above are Postbatch's own limits.