HEIC to PDF without losing quality: what actually survives

What survived in the measured HEIC-to-PDF tests?

Source: GoPDFConverter HEIC-to-PDF Compatibility and Privacy Lab. Download the full results CSV for file sizes, dimensions, formats, alpha, metadata, color-profile status, render metrics, and SHA-256 checksums.

Does converting HEIC to PDF reduce quality?

It changes the encoded image even when it retains every decoded pixel position. Ordinary opaque HEIC photos are decoded to pixels and then encoded again as JPEG at quality 92 before PDF embedding. Across the four opaque fixtures, mean absolute RGB-channel error ranged from 1.120 to 4.957. The 2400 × 1600 hard checkerboard produced the largest change because JPEG handles sharp alternating edges poorly.

That is not the same as shrinking the image dimensions. A 2400 × 1600 source remained 2400 × 1600 inside the PDF. For ordinary photos, the small measured pixel changes may be visually acceptable; for archival preservation, scientific imagery, exact graphics, or prepress work, keep the HEIC and use a color-managed workflow.

Choose Auto, A4, or Letter deliberately

Auto does not read the HEIC’s capture-density metadata and invent a print size from it. The useful print measurement is effective PPI = decoded pixels ÷ placed inches. For ordinary documents, A4 or Letter usually communicates intent more clearly than a very large Auto page.

How to convert one or multiple HEIC photos to PDF

1. Keep the original photos.

   The PDF is a derivative for sharing or printing, not a replacement for the HEIC container, metadata, color profile, or exact source bytes.

2. Add the HEIC or HEIF files.

   Use the local browser converter. Add multiple files when every photo should become a separate page in one PDF.

3. Arrange the page order.

   Put receipts, evidence photos, assignments, or report images in the final sequence before conversion.

4. Choose page size, orientation, and margin.

   Use A4 or Letter for normal documents. Use Auto only when its pixel-to-point physical size is desired.

5. Create the PDF locally.

   The browser loads decoder code, decodes each primary HEIC image, chooses JPEG for opaque photos or PNG for detected transparency, and assembles the PDF.

6. Verify the download.

   Check page count, orientation, alpha edges, color appearance, physical page size, effective PPI, and output bytes. Large batches can be limited by browser memory.

Orientation, transparency, metadata, and Display P3

Orientation

The orientation-6 fixture stored a 1200 × 800 pixel matrix but was intended to display upright at 800 × 1200. The production decoder applied that orientation once. The PDF embedded an upright 800 × 1200 image; the source EXIF orientation tag itself was not copied.

Transparency

Transparent HEIC follows a lossless PNG path instead of opaque JPEG embedding. The validated fixture produced an 800 × 600 PNG image with an 800 × 600 PDF soft mask, avoiding the black-background failure that existed before the v85 fix.

Metadata

The tested EXIF description and synthetic capture dates were removed. This can reduce accidental sharing of source metadata, but it is not a universal scrubbing guarantee for every HEIC structure. Inspect the actual PDF if metadata removal is operationally important.

Display P3 color

The P3 gradient decoded and retained its 1000 × 700 dimensions, but its ICC profile was not embedded in the PDF. Browser canvas handling can normalize color. Do not rely on this path for color-managed print delivery or archival preservation.

Why can the PDF be larger than the HEIC?

HEIC uses efficient HEVC compression. The converter must decode it, encode an opaque image as JPEG or a transparent image as PNG, and then add PDF page and object structure. The 44,092-byte landscape HEIC became a 58,297-byte PDF, while the 124,002-byte high-detail HEIC became a 133,409-byte PDF. Smaller output is not a promise of HEIC-to-PDF conversion.

Compress the finished PDF only when delivery size matters more than exact current pixels, and inspect the result. Recompressing a newly encoded JPEG can compound loss.

Can HEIC-to-PDF conversion stay private?

In the published Chrome trace, selecting and converting a 44,092-byte fixture triggered public decoder/library GET requests, browser-local blob: reads, and analytics requests. No conversion API was called, and no remote request body matched the input or output bytes. The analytics completion event contained the tool name and output size, not the photo content.

“Local” therefore means the selected HEIC and generated PDF bytes are not uploaded for conversion. It does not mean the webpage makes zero network requests. You can reproduce the check with a synthetic fixture and the two-minute browser network test.

HEIC to PDF vs HEIC to JPG vs keeping HEIC

Frequently asked questions

Use the evidence, not a generic lossless claim