Input
HEIC
Output
JPG
Runtime
Browser

Convert HEIC to JPG Online

Create a widely compatible JPEG from a supported HEIC photo directly in your browser.

Local processingNo sign-upBatch and ZIP export

Convert on this device

Files stay in this browser tab. Nothing is uploaded to Tool Swim.

Private by design

Drop HEIC files here

Up to 8 MB per file, 4 files, and 24 MB of source data per batch.

Multi-image HEIC files export the first decodable image only.

These conservative limits apply because compressed dimensions cannot always be verified before the browser codec expands the image.

What the output keeps

Metadata

Canvas output removes EXIF, GPS, captions, and most embedded metadata.

Animation

Animated or multi-image input becomes one static decoded frame.

Color profiles

The browser decodes color before export; wide-gamut and HDR appearance can change.

A practical guide

Example: IMG_4821.HEIC → IMG_4821.jpg

Prepare an iPhone photo for a school form, marketplace listing, or Windows application that does not accept HEIC.

Use JPEG when HEIC is rejected

HEIC is a common container for efficient photos captured by Apple devices, but support remains uneven in upload forms, older operating systems, browsers, and editing software. JPEG is a practical compatibility copy for photographs because it opens almost everywhere. Conversion leaves the HEIC source untouched and creates a new file for the destination that needs it.

JPEG uses lossy compression. Even when the HEIC source looks excellent, the new encoder approximates its decoded pixels. Choose a high quality setting for faces, documents, or detailed scenes and keep the HEIC in case you need another export later.

Browser decode support is the first requirement

A valid HEIC file may fail before conversion because HEIC decoding is not consistently available across browsers and platforms. Support can depend on the operating system codecs behind the browser, not just the browser version. Updating the browser may help, but it cannot add a missing system decoder in every environment.

If the file cannot be opened, try a current browser on the device that created the photo or use the operating system's export feature. A server or native desktop converter with an HEIF decoder is another option. A decode failure does not necessarily mean the photo is corrupt.

Understand which image is selected

HEIC containers can hold more than one image, including burst frames, depth information, thumbnails, or paired content. A basic browser conversion exports the primary decoded image rather than every item in the container. Motion Photo or Live Photo behavior is not preserved in a static JPEG. The result contains one still frame.

Review the JPEG to ensure it is the expected view and orientation. If you need a depth map, alternate exposure, or the video portion of a Live Photo, use software that understands those container relationships and can export each resource deliberately.

Expect metadata and color differences

Phone photos often contain capture time, location, camera settings, orientation, and device details. Canvas-based output normally strips that metadata. This can be useful for a public upload where privacy matters, but it is unsuitable as the only archival copy. Retain the HEIC if dates, location, or provenance are important.

HEIC photos may use wide-gamut color or HDR-related information that ordinary JPEG and browser canvas output cannot represent in the same way. ICC and color handling depend on the platform and decoder. Highlights, saturation, or tone can therefore differ. Use a color-managed native export for print, HDR, or exact photographic work.

Metadata removal also changes how photo libraries sort and group the derivative. If the JPEG must join a case record, project archive, or family timeline, capture the original date and source in the filename or catalog before conversion. Do not publish a location-bearing original merely to preserve its date; keep the private master and attach only the minimum descriptive information needed to the shareable JPEG.

Check the compatibility file

Open the JPEG and inspect faces, text, gradients, and shadow detail at 100 percent. Confirm width, height, orientation, and file size. Then test the actual form or application that prompted the conversion. Some services impose both a format rule and a dimension or byte limit, so a valid JPEG may still need a deliberate resize.

Name the result for its purpose and avoid replacing the HEIC. If the destination applies its own compression, do not reduce quality more than needed during the first export. Starting from the original again is the safest way to create a different version.

Before processing a group of phone photos, convert one image captured in the same camera mode and examine the entire path. Portrait mode, night mode, screenshots, and downloaded HEIC files can have different dimensions, color characteristics, or auxiliary resources. Check whether the visible orientation matches the phone, whether highlights and skin tones remain natural, and whether the receiving service crops to a fixed aspect ratio. If chronological sorting matters, remember that a stripped JPEG may no longer carry the capture timestamp; put the date in the filename or preserve it in your asset record. This small trial prevents a batch of compatible files from losing context or arriving with a shared color problem.

Questions and answers