Convert HEIC to PDF
Your camera roll as one document. The photos never leave this tab.
Runs in your browser0 bytes uploadedYour camera roll as one document. The photos never leave this tab.
Runs in your browser0 bytes uploadedDrop your HEIC photos here
or paste Ctrl+V
The whole camera roll at once is fine. Nothing is uploaded — the document is written here, from bytes that never leave this tab.
Nothing on your phone broke. Apple switched the default camera format in 2017, and every iPhone since has been saving pictures as HEIC unless someone went into Settings and changed it back. The reason is straightforward: the same photograph, at the same visible quality, takes up roughly half the space. Across a few thousand holiday pictures that is real money in storage, which is why the switch happened and why it is not going to be reversed.
The catch only shows up when the picture leaves the phone. Inside Apple's world everything reads HEIC without complaint. Send one to a colleague on Windows, attach it to an insurance claim, or drop it into a submission form, and you discover that a great deal of software has never heard of it. That is usually the moment somebody goes looking for a way to turn a camera roll into a document instead.
Hand the photos to the panel above, put them in the order you want, and press the button. There is no account, no email address, no watermark, and no queue. What makes that possible is that the work happens on your own machine: the JavaScript on this page reads the bytes your browser already loaded from disk, decodes them, and assembles the document right there in the tab you are looking at.
That is worth stating plainly because it is unusual. The other results for this search all work the same way as each other — your pictures travel to a server somewhere, get converted, and come back as a download link. Those services are not necessarily doing anything sinister with them, but you are trusting a stranger with the contents, and you cannot check afterwards what was kept. Here there is nowhere for a photo to go. You can prove that to yourself in about ten seconds: open the developer tools, switch to the network panel, and run a conversion while you watch. Nothing outbound will contain your picture, because there is no address on this site that would accept one.
One consequence of working locally is that the ceiling is your own hardware rather than somebody's free tier. Thirty photographs at once is an ordinary batch, not an upsell moment. If a batch is big enough to make a laptop sweat, the page says so before it starts rather than after the tab has already died.
This comes up constantly, and the answer is not that Adobe forgot. A HEIC container stores its picture using HEVC, the same compression scheme used for video. Decoding it requires a licensed decoder, and the licensing for that codec is genuinely awkward — which is why support arrived slowly and unevenly across the industry, rather than all at once. Acrobat can place a JPEG or a PNG into a document without thinking about it, and simply has no route for the other thing.
The same limitation applies to the finished document, and it explains something you might otherwise find strange further down. A PDF cannot store a HEIC picture either. No reader on any platform would be able to draw it. So a converter has exactly one honest option, which is to decode each photograph and write it back out in a format documents have understood for thirty years.
If you have used one of these converters before, you may have met the classic failure: half your pictures come back rotated, and no setting seems responsible for it. It is not carelessness by one particular website. A phone camera never turns its sensor when you turn the phone. It records the same frame every time and attaches a note saying which way up the result should be displayed. Your camera roll reads that note, and so does every picture viewer you have ever used.
A document has no equivalent note, so the turn has to be resolved on the way through. Here it is resolved at the earliest possible moment — while the photograph is being decoded, which is where the instruction already lives inside the container. By the time anything is measured or placed, the picture is the right way up and its width and height have already swapped over. A portrait shot therefore gets a portrait page, at the correct proportions, rather than a landscape one with a squashed picture in the middle of it.
The order of those two steps matters more than it sounds. Applying the turn a second time, when placing the picture on the page, would land it back on its side — and that particular mistake only shows itself on the photographs that needed the correction, which is exactly the set nobody has in their test files.
Expect growth, and sometimes a lot of it. Since every picture has to be re-encoded on the way in, and the format documents accept is roughly half as efficient as the one your phone used, the arithmetic works against you. A tightly compressed camera file can grow more than tenfold. That is not waste; it is the price of a file that opens everywhere.
Two things on this page exist because of that. The first is the quality slider, which controls the trade directly and is worth touching before a large batch. The second is the estimate above the button, which is calculated from the number of pixels rather than from the size of what you handed in — a shortcut based on the incoming file size sounds sensible and turns out to be wrong by a factor of twenty on heavily compressed originals. The receipt afterwards shows what the file actually came to, so you can see how close the forecast landed instead of taking it on faith.
If the result is still larger than you want, the honest fix is to reduce the pictures first rather than to squeeze the document afterwards. That is a separate job with its own page: compress an image to an exact size. And if what you actually needed was ordinary picture files rather than a document, HEIC to JPG is the shorter route, withHEIC to PNG alongside it when you want no further loss.
There is no reverse direction here, and that is a decision rather than an omission. A page turning documents back into HEIC could not work: no browser can write that format. They can read it, on a good day, but the encoder is part of the operating system and is not offered to web pages. Building the page anyway would mean quietly shipping your file to a server, which is the one thing this site refuses to do. If you want pictures out of a document, PDF to JPG is the page for that, and JPG to PDF handles the direction you are on now when the pictures have already been converted.
Live Photos lose their moving half, because a page in a document holds one still image and there is nowhere for a short video to live. The frame you get is the same one your camera roll shows as the photograph, and the receipt names any file where that choice was made instead of letting it pass unmentioned. Location data is left behind for the same reason it should be: a picture straight out of a phone carries the coordinates of the place it was taken, and a document has nowhere to display them, so carrying them along would preserve the risk without producing any benefit. If you want to see exactly what your files are carrying before deciding any of this,what HEIC actually is covers the container in more detail.
No. On Safari the photos are decoded by the same HEIC support macOS and iOS already use for the Photos app, and everywhere else a decoder is downloaded once and run inside this tab. The PDF is assembled here too. That matters more for this format than for most: a HEIC straight out of an iPhone carries the coordinates of the place it was taken, and handing that to a stranger to make a document is a bad trade.
Because a PDF cannot carry HEIC. No PDF reader can decode the video codec HEIC is built on, so every photo has to be decoded and written again as JPEG, and JPEG is roughly half as efficient. A heavily compressed HEIC can grow more than tenfold on the way through. The quality slider is there for exactly this reason, and the estimate above the button is calculated before you commit to anything.
No, and this is the single most common failure in this category. A phone never turns the sensor; it records a landscape frame and writes a note saying which way up to show it. Here that note is read before anything is planned, so a portrait photo gets a portrait page, and the turn is applied while the photo is decoded rather than a second time on the page. Photos that carry a turn are named on the receipt.
Yes — one, two or four per page, which turns a camera roll into a contact sheet instead of a stack of full-page images. The page count updates as you choose, so the effect is visible before you run anything, and the order is yours to set with the arrows next to each row.
A HEIC from a burst or a Live Photo holds several images in one container. The primary one is used — the same frame the Photos app shows you — and the receipt says so rather than quietly picking whichever image happened to be stored first, which is a different picture surprisingly often.
No, and it is not an oversight. No browser can encode HEIC; they can only read it. Apple ships the encoder as part of the operating system and does not expose it to web pages, so a PDF to HEIC page here would either not work or would quietly hand your file to a server, which is the thing this site exists to avoid. If you want images out of a PDF, that is PDF to JPG.