How to use an image converter without uploads
ImageForge is useful when you want to change the format of work images or unpublished photos without uploading them. Conversion runs in your browser from file selection to saving the result.
Open tool →Steps
- Select images or a folder in ImageForge and check the count and input formats.
- Choose output format, quality, dimensions and metadata settings.
- Inspect the output and save individual files or a ZIP to your device.
File selection screen

Choose the result you actually need
On your first visit, try one image through to download before selecting the full collection. Local processing does not remove the need to check download folders and filenames on a shared computer.
Checks before saving
Avoiding uploads does not guarantee the safety of the device, browser extensions or a shared computer. Inspect output content and filenames before publishing, and keep important originals separately. Check your organization’s rules for confidential documents.
The browser reads selected files. Images can be decoded and re-encoded using Canvas or WebAssembly. Web Workers separate supported processing from the interface, but do not create unlimited memory. A small compressed input can occupy much more memory after decoding.
Troubleshooting
Check format support and browser version, then test a few files through to saving. A computer may be better for large tasks. If a phone heats up, pause and let it cool; save results before closing the browser.
ImageForge conversion measurements
These ImageForge measurements were supplied on 6 October 2026. Environment: Firefox, Windows 11, Ryzen 7 2700X and 32GB RAM.
| Task | Images | Elapsed time |
|---|---|---|
| AVIF → JPEG | 206 | 4 seconds |
| HEIC → JPEG | 45 | 59 seconds |
| PNG → WebP | 206 | 9 seconds |
| JPEG → WebP | 206 | 9 seconds |
| JPEG resize to 1920px | 206 | 4 seconds |
| PNG → JPEG | 206 | 5 seconds |
| WebP → PNG | 206 | 6 seconds |
Input size, output size, quality settings and whether initial engine loading was included were not recorded for this batch. These are not reduction percentages or quality-80 results. Timing varies with image content, dimensions, device and browser; matching speed is not guaranteed. The previously published 197-image, 42.8MB, quality-80, 8-second test is a separate record.
Measurements using generated files in the public tools
On 6 October 2026, we processed generated test files in the public PikaPika App tools, downloaded the outputs and validated them. These are separate from the measurements supplied by the user.
Windows 11 Home, Ryzen 7 2700X, 32GB RAM and Chrome 154.0.8037.93 in automated headless mode; not Firefox.
Generated 1600×1200 patterns were used, not photographs. Their compression ratios are not representative of photographs. The metadata test checked a generated manufacturer and date; GPS data was not included.
| Test conditions | Input size (bytes) | Output size (bytes) | Time (seconds) | Saved-output validation |
|---|---|---|---|---|
| 20 images (generated pattern) · webp · quality 80 · two subfolders | 3,381,740 | 789,665 | 2.076 | 20 items · ZIP file count and integrity checked |
One observed run per task. Timing starts at the start-button click and ends when the tool reports completion, including engine initialization. Page loading, file selection, downloading and validation are excluded. Browser asset caches were shared between runs. These are not averages or speed guarantees. Automation and completion-state detection add overhead, so sub-second results are not suitable for precise processing-speed comparisons.
Frequently asked questions
Why can a large image batch take time to save?
Compressed file size differs from decoded memory usage. Parallel processing and ZIP creation also need memory. If a phone gets hot or stops, use smaller batches or a computer.