Trust and privacy

What happens to the file

  • Files stay on your device for core image work. Picmu does not upload them.
  • The original file stays untouched while you preview changes and export a new copy.
  • Unsupported formats are flagged early instead of failing after a long wait.
  • Batch jobs are still browser-only. Files are not sent off-device for hidden server-side conversion.

Quick flow

How to use this page with confidence

  1. Drop multiple files anywhere on the page to build the queue quickly.
  2. Set the shared export logic, then override the selected file only if needed.
  3. Process locally, review statuses, and download the completed run as a ZIP archive.

Benefits

Why this page is useful

Run multi-file image conversion locally with queue control, shared settings, per-file overrides, and ZIP export.

Made for repeated production work

Queues, statuses, retries, and ZIP export turn a folder workflow into a clear local process instead of a one-file-at-a-time chore.

Shared settings without losing control

Apply a consistent export to many files, then override the selected item when one asset needs a different output.

Strong fit for delivery workflows

The batch route is useful for website assets, client handoffs, content packs, and other multi-file exports.

Tradeoffs

What to consider before export

One preset rarely fits every file perfectly

Shared settings speed up the job, but representative testing still matters because one queue can contain very different images.

Naming patterns matter in larger runs

A clear output pattern helps avoid confusion once you start exporting many related files.

Batch conversion still depends on codec support

Capability notices remain visible because a large queue does not change what the current browser can or cannot encode.

Best practices

Keep the output reliable

  • Test the workflow on a representative file before running the full queue.
  • Use a naming pattern that makes the output obvious once zipped.
  • Keep one queue focused on one destination when possible, such as web delivery or print prep.

FAQ

Questions before you export

Yes. The queue, processing, and ZIP export stay in the browser for core image workflows.

Open in Picmu

Open the batch image converter

Batch pages start from shared settings, but you can still override a selected file when a single asset needs a different output.

Open the batch image converter