When to use a PDF (and when not to)
PDFs are everywhere, but they're not always the right tool. Here's when a PDF is exactly what you want, and when another format would serve you better.
The PDF is so common that people reach for it by default, sometimes for things it’s genuinely bad at. It’s a brilliant format for some jobs and an awkward one for others. Knowing the difference saves you (and whoever you send files to) a lot of friction.
What a PDF is actually for
The whole point of a PDF is that it looks the same everywhere. Open it on a phone, an old office PC, or a print shop’s machine, and the layout, fonts, and spacing stay put. It’s a fixed, finished page, like a printed sheet that happens to be digital. That’s its superpower, and it’s why a PDF shines for:
- Final documents meant to be read or printed, not edited. Contracts, invoices, reports, certificates, anything where the layout matters and you don’t want it shifting.
- Sharing across different devices and software. When you don’t know what the recipient is using, a PDF is the safe bet that it’ll look right.
- Combining different things into one file. Text, images, and scanned pages can all live in a single PDF, which is why merging documents or turning images into a PDF is so handy.
- Long-term keeping. With the archival PDF/A variant, a PDF is built to still open correctly years from now.
If your goal is “send a finished thing that looks right and stays put,” a PDF is exactly the tool.
When a PDF is the wrong choice
The same fixedness that makes a PDF great for finished documents makes it a poor fit for others:
- Content that’s meant to be edited. If you’re sending a document for someone to change, a contract still being negotiated, a report being co-written, a PDF fights you. A PDF is for the final version; collaborative editing belongs in a word processor or a shared document.
- Data meant to be sorted or calculated. Putting a table of numbers into a PDF freezes it into a picture of a table. If someone needs to sort, filter, or do maths on it, they need a spreadsheet, not a PDF. (Extracting it back out later is extra work that didn’t need to exist.)
- A single image you just want to show. If all you have is one photo or a screenshot, a plain image file (JPG or PNG) is simpler and lighter than wrapping it in a PDF. Reach for a PDF when you’ve got several images to bundle, not one to display.
- Content for the open web. A web page reflows to fit any screen; a PDF doesn’t. For something people read in a browser, especially on phones, a web page is friendlier than a PDF they have to pinch and zoom.
A simple test
Ask one question: is this finished, and does it need to look the same for everyone? If yes, a PDF is right. If the thing still needs to be edited, sorted, calculated, or read comfortably on a small screen, something else will serve you and your recipient better.
When a PDF is right, do it privately
When a PDF genuinely is the answer, you’ll often be assembling one from documents or images, and those are frequently personal: contracts, scans, ID photos. files.co builds PDFs in your browser, merging files or turning images into a PDF on your own machine, with nothing uploaded. You can confirm it with DevTools (F12) or by working offline.
So treat the PDF as what it is: the right tool for a finished, fixed, shareable document, and the wrong one for things still in motion. Pick it when it fits, skip it when it doesn’t, and when you do need one, build it in your browser without the file ever leaving your machine.