Convert JPG to PDF

The portal only takes PDF. Your document is a PNG.

It is the last step before submitting and it should take ten seconds. It usually does not, because the first result comes back too heavy or the wrong shape.

The 5 reasons, in plain words

• PNG is lossless, and that is the problem here. PNG stores every pixel exactly, which is right for a screenshot and wasteful for a photographed page. Wrapped unchanged in a PDF, the weight comes with it.
• A PDF has a page size; a PNG does not. An image is just pixels. A PDF places them on a page. Get the DPI wrong and the same document becomes Letter, A4 or a strip — and some portals check.
• Multi-page matters. Several PNGs usually need to arrive as one PDF in order, not as separate files. Portals that ask for a single document mean it literally.
• Re-encoding is where the size is won. Converting the image to JPEG inside the PDF, at a target size, is what turns 20 MB into under 2 — and for a photographed document it costs nothing visible.
• Screenshots are a separate trap. A screenshot of a document is a photo of a screen: low resolution and often rejected on its own merits, whatever container you put it in.

Which of them can software fix?

All of it, in one step. You choose the page size and the resolution, the image is re-encoded to the exact weight you need on the way in, and several images can go in as one ordered document. It runs in this browser — the file is never uploaded anywhere to be converted.

Convert a HEIC photo to PDF

Your iPhone took the photo in HEIC. The portal wants a PDF. Almost every free converter online solves this by taking a copy of your document onto their server — which, for a passport or a tax form, is a bad trade for something a browser can do on its own.

Where it works: the HEIC photo is opened by your own browser. Safari on iPhone, iPad and Mac opens HEIC, so do this on the iPhone that took the photo. Chrome, Edge and Firefox on a computer cannot open HEIC: there DocSupra says so instead of guessing, and you can export the photo as JPEG first or open this page on the iPhone.

Why the portal will not take it

HEIC is a container built on the HEVC video codec, and HEVC carries patent licensing. Web servers, document management systems and government intake pipelines mostly skipped it for that reason. So the file is perfectly good and the portal simply has no code that can open it.

Three ways to fix it, best first

Stop your iPhone making HEIC in the first place

Settings → Camera → Formats → Most Compatible. From then on the camera saves JPEG. This does not convert the photos already in your library.

Emailing it to yourself sometimes works, and sometimes ruins it

Mail often converts HEIC to JPEG on the way out, which is why the trick has a reputation. It also frequently downsizes the image to save bandwidth, and a downsized photo of a document can drop below the resolution a reviewer needs. If you use this route, check the pixel dimensions of what arrives.

What to aim for

1. Straighten and even out the lighting before converting.
2. Export at 300 DPI for a document page — enough to read, not so much that it blows the size cap.
3. Check the finished PDF against the portal's own limit: 12 MB at USCIS, 15 MB at the IRS, often 2–5 MB at job and school portals.

“File type not supported” — your iPhone saved it as HEIC

You photographed the document, the portal refused it, and nothing looks wrong with the picture. Almost always the problem is the format, not the photo: since 2017 iPhones save as HEIC by default, and most government upload forms only take JPEG, PDF or PNG.

Where it works: the HEIC photo is opened by your own browser. Safari on iPhone, iPad and Mac opens HEIC, so do this on the iPhone that took the photo. Chrome, Edge and Firefox on a computer cannot open HEIC: there DocSupra says so instead of guessing, and you can export the photo as JPEG first or open this page on the iPhone.

How to tell that this is your problem

Any one of these is a giveaway:

• The file name ends in .heic or .HEIC.
• The portal says file type not supported, invalid format, or just fails silently.
• The photo opens perfectly on your iPhone but looks broken or will not open on a Windows PC.
• You emailed it to yourself and it arrived as a .jpg — iOS converts on the way out, which is why the same picture sometimes works and sometimes does not.

Why portals reject it

HEIC (High Efficiency Image Container) stores the same picture in roughly half the space of a JPEG. Apple made it the default in iOS 11. The trouble is that the software behind an upload form is often older than that, and a reviewer opening the file on a government workstation may have nothing that can read it. Rather than risk an unreadable submission, the portal refuses the format outright.

It is not a judgement about your photo. A perfect, sharp, well-lit HEIC is rejected exactly as fast as a bad one.

Which format should you convert to?

Stop it happening again

1. Open Settings on your iPhone.
2. Tap Camera, then Formats.
3. Choose Most Compatible.

From then on the camera saves JPEG. Photos already in your library stay HEIC — this only changes what happens from now on.

Several pages, one upload slot

A portal gives you one field and you have five pages. Merging them is easy; merging them and still landing under the size cap is where it goes wrong, because five phone photos in one PDF is routinely 25 MB against a 12 MB limit.

Why the obvious order fails

The instinct is: merge the photos, then squeeze the PDF until it fits. That fails because a raw phone photo of a page is mostly not the page — it is shadow gradient, desk texture and sensor grain. Compression spends its budget describing all of that, and to reach the target it has to take the bits from somewhere. It takes them from the text.

Flatten the lighting and straighten the page first and the photo becomes largely flat white with sharp black marks, which is the easiest thing in the world to compress. The same five pages then reach the same file size with the text untouched.

The order that works

1. Correct each page. Even out the lighting, remove glare, straighten the angle. This is what makes the rest possible.
2. Set the resolution to 300 DPI. Higher adds size without adding legibility.
3. Merge into one PDF, in the order a reviewer expects to read them.
4. Set the size target on the finished file, not on each page. Compression works better across the whole document.
5. Check the last page. Merges truncate silently more often than you would think.

Page order matters more than people think

A reviewer opening your file expects the cover letter first, then the evidence in the order your letter refers to it. A PDF where page 4 is the first thing they see does not fail a technical check, but it does make a person read your submission twice — and a request for evidence costs weeks.

The portal wants one file. You have two photos.

This is the most common two-minute task that takes an hour: find a converter, find a merger, lose the order, end up with a 14 MB file. It is one step when the software knows what a card is.

The 5 reasons, in plain words

• Two photos, one document. Portals index documents, not photos. A second file is a second document to them, and a second document named the same is a mistake.
• Order is part of the document. Front first, then back. A merger that sorts by file name puts them the way the camera numbered them, which is whichever side you shot first.
• The table around the card. A phone photo of a card is mostly table. Left in, it doubles the file size and shrinks the card to a corner of the page.
• Each side at an angle. Cards photographed from above are rarely square to the lens. Two sides at two different angles look like two different documents.
• The weight limit applies to the whole file. One PDF with two full-size photos inside can weigh 15 MB. The limit is on the file you send, not on each picture.

Which of them can software fix?

All of it, in one pass. Drop both photos, choose the document class and the destination; each side is found by its edge, straightened and cut to the card with the colour kept, then placed as page 1 and page 2 of one PDF at 300 DPI and under the size cap the destination publishes, or the one you set. If a side is too blurred to read, it says so instead of shipping it. It runs in this browser; the card with your name on it never leaves your device.

Photo to PDF, and what actually changes when you convert

A PDF is a container. Wrapping a photo in one does not compress it, does not sharpen it, and does not fix the lighting. What it does change is three things portals care about: the declared page size, how it prints, and whether the file is accepted in the first place.

What conversion changes, and what it does not

The page size trap

A photo has pixels but no physical size. A PDF page does. When a converter is not told what page size to use, it picks one — and the result prints at whatever scale that choice implies. A page meant to be Letter can arrive as a slightly different size, which is enough for some filing systems to flag it.

If the document is a Letter page, say so at conversion time. If it is an ID card or a photo, a fitted page is usually the right answer instead.

Why the PDF came out bigger than the photo

Two common reasons. The converter re-encoded the image at a higher quality than the original, or it stored it without compression at all. A lossless PDF of a full-resolution phone photo can be several times the size of the JPEG it came from — which then runs straight into the upload limit.

Multiple photos, one PDF

Portals that ask for "the document" usually mean all of it: front and back, every page, in order, in one file. Uploading four separate images where one multi-page PDF was expected is a common reason a submission comes back marked incomplete.

Keep the pages the same size and the same orientation. A PDF where page 2 is landscape and half the resolution of page 1 reads as carelessness to whoever opens it.

The order that avoids re-doing it

1. Fix the photo first — straighten it, even out the light.
2. Decide the page size: Letter, A4, or fitted to the image.
3. Convert, then check the resulting file size against the portal limit.
4. If it is over, reduce the resolution rather than the quality — the letters survive better.