filename.heic
Queued—
The client sent a folder of iPhone photos and InDesign will not place a single one. Convert the batch below and get on with the layout.
100% Local — Client Assets Never Leave Your Device
Drop the client's photos here
or pick them from your device — a full asset folder at once is fine
Supports .heic and .heif from iPhone, iPad and modern Android cameras
95% for print and layout work. Artefacts compound through every export.
filename.heic
Queued—
InDesign, Illustrator, Affinity and QuarkXPress all place a fixed set of raster formats, and HEIC is not among them. Where an application does open it, that support is usually inherited from the operating system — which is why it works on your Mac and fails on the studio PC.
Print workflows compound the problem downstream: preflight tools, RIP software and printer portals were built around TIFF, JPEG and PDF, so a HEIC that made it into a layout would fail later, at the worst moment.
Resolution is preserved exactly, so a 12 MP client photo arrives at 4032 × 3024 — enough for a sharp 13 × 10 inch placement at 300 DPI. Nothing is downscaled.
Output is 8-bit sRGB with no embedded profile. For CMYK print work you will be converting profiles in your layout software anyway, but it is worth knowing the wide-gamut P3 data an iPhone captures is not carried through.
Drag it onto the box above or press Select Files. Everything that is not a HEIC is skipped.
Take the batch as one ZIP, unzip into your links folder, and place as normal.
Client confidentiality holds.
Conversion happens inside your browser, so an unreleased product shoot or an embargoed campaign asset is never uploaded to a third-party converter. That is usually the difference between a tool you can use on client work and one you cannot.
No. Both place a fixed set of raster formats that does not include HEIC. Where an Adobe application opens one at all, it is borrowing the operating system's decoder — which exists on macOS and generally does not on Windows. Converting to JPG makes the asset behave identically on every machine in the studio.
For most placements, yes. Pixel dimensions are untouched, so a 12 MP photo supports a sharp A4 placement at 300 DPI. Output is 8-bit sRGB without an embedded profile, so handle colour conversion in your layout software as you would with any client JPEG.
No. The decoder is a WebAssembly module that runs inside your browser tab, so the photo is read from your device into memory and converted there. You can check it in your browser's Network tab, or disconnect from the internet once the page has loaded and convert anyway.