Does BatchMint currently process images in the cloud?
No. The deployed workspace uses the local processing engine. A future cloud engine is an architectural extension, not a current product capability.
Last reviewed: July 23, 2026
Product facts
BatchMint is a static browser application that processes up to 20 JPEG, PNG or static WebP inputs locally and exports JPEG, PNG, WebP or AVIF. This page separates implemented behavior from future plans and marketing assumptions.
What the current build is
BatchMint is a static Astro website with a React image workspace. The deployed product is a browser application rather than a hosted image-processing API: transforms run behind the local processing engine in Web Workers, and completed files return to the page as browser Blobs for review and export. Planned cloud processing is not presented as a current capability.
Current inputs, outputs and batch limit
| Area | Implemented behavior | Important boundary |
|---|---|---|
| Input | JPEG/JPG, PNG and static WebP | No HEIC/HEIF, PSD, RAW, TIFF, video or animated-image input |
| Output | JPEG, PNG, WebP and AVIF | Destination software still needs to support the chosen format |
| Batch | Up to 20 selected images | The limit protects local memory and CPU on ordinary devices |
| Resize | Maximum width with aspect ratio preserved | Smaller sources are not enlarged |
| Target size | Bounded quality search for JPEG and WebP | The requested byte target is not guaranteed for every source |
| Watermark | Text or transparent PNG/WebP logo; nine-grid or tiled placement | Watermarks do not guarantee that an image cannot be copied |
Fixed processing order
- Identify the file and validate the supported type.
- Read and correct JPEG orientation before other transforms.
- Resize without enlarging a smaller source.
- Apply an optional text or logo watermark after resizing.
- Encode to the chosen format and run target-size search where supported.
- Render the output name, then export individual files, a folder, ZIP volumes or a CSV report.
Worker and device behavior
Heavy decoding, resizing, watermarking and encoding run outside the main interface thread in local workers. Desktop processing uses no more than four workers, while mobile uses one to reduce decoded-image memory pressure. A cancelled job stops queued work and completed object URLs are released when the interface no longer needs them. Device speed, memory and browser implementation still affect the experience.
Privacy and network facts
| Data or request | Current behavior |
|---|---|
| Selected image bytes and decoded pixels | Remain in the page and local workers |
| Original filenames and watermark text | Not included in BatchMint application network requests |
| Presets and brand kits | Stored in the current browser profile through IndexedDB |
| Website assets | HTML, JavaScript, CSS, fonts, service worker and codec assets are downloaded normally |
| Advertising | Public content pages may load approved advertising; the workspace excludes the AdSense site script |
Export and local persistence
Finished files can be downloaded individually, written to a user-approved folder where the browser supports File System Access, or collected into ZIP volumes. The CSV report records processing outcomes without sending the batch to BatchMint. Presets and brand kits stay in the current browser profile and are removed when that site storage is cleared; BatchMint does not synchronize them across devices.
What the product does not currently do
- It does not upload results directly to Shopify, Etsy, Amazon or another marketplace.
- It does not provide cloud collaboration, account-based image history or cross-device preset synchronization.
- It does not promise a universal compression ratio, identical quality numbers across codecs or an exact target size for every image.
- It does not claim that local processing controls browser extensions, device software or services to which a user later uploads an export.
Evidence and correction path
- Testing methodology
How product facts, network privacy and encoded-byte evidence are checked.
- Reproducible compression benchmark
Deterministic fixtures, encoder versions, settings and exact byte results.
- Contact and corrections
Report a product-fact error to the published project address.
FAQ
How many images can one batch contain?
The current limit is 20 JPEG, PNG or static WebP inputs per batch.
Are product defaults marketplace requirements?
No. Presets and starting values are workflow conveniences. Current Shopify, Etsy, Amazon or other platform rules must be checked separately before upload.