Are files uploaded to a server? What does browser-side processing mean?

What does browser-side processing mean here?

After you add files, the main conversion work runs in the browser on the device you are using.

In practical terms, that means:

• The tool is not based on uploading files first and waiting for results to come back
• Speed and stability depend partly on the device and browser you are using
• Larger files and larger batches put more strain on that device

How does that affect privacy, speed, and device differences?

For normal use, it means the work stays on your device instead of being sent somewhere else for conversion first.

It also means the device pays the cost. If the batch is large, the files are large, or the browser is already busy, the job may slow down or feel less stable.

The same files can feel fine on a desktop and heavy on a phone.

What browser-side processing does not guarantee

Running the conversion in the browser does not guarantee all of the following:

• Every file will convert cleanly
• Every run will finish quickly
• Every device will feel the same
• All metadata will stay fully intact

If a file is damaged, saved differently, or part of a batch that is too large for the device, you may still see failed conversions, slowdowns, or Download All issues.

What happens to EXIF and other metadata?

Browser-side processing is not the same thing as full metadata preservation.

This tool keeps EXIF where it can, but it is not designed around perfect preservation.

If you just need HEIC files converted to JPG / JPEG for everyday use, that is often enough.

If complete EXIF or metadata preservation matters, a dedicated local tool is the safer choice.

When is staying in the browser a good fit?

Staying in the browser is usually a good fit when:

• You want to convert iPhone photos to JPG / JPEG for everyday use
• You want files in a more widely supported format quickly
• The file count is not extremely large
• Complete metadata preservation is not a requirement

When are desktop or local tools a better fit?

A desktop workflow or local tool is usually the better fit when:

• You need to process a very large number of files at once
• The device already feels overloaded
• You are already seeing slowdowns, failed conversions, or Download All problems
• You need EXIF or other metadata preserved as completely as possible
• You want longer runs with less dependence on browser conditions