Design
Formatting PDF Guides for Mobile Readers
By AI Creation Forge · 8 min read
The Direct Answer
Format a PDF guide for a phone by keeping one column, leaving real margins, setting body type you can read without pinching, and keeping images light enough that the file opens on a mobile connection. Then open the exported file on a phone and try to do one task from it. Tags, alt text, and screen readers are part of the same job and are covered in the accessibility article linked below. This page is the production pass that comes before that test.
Picture Diego in a break room on Wednesday at noon, holding his phone in one hand and a sandwich in the other. He bought a scheduling guide that morning. The cover looked sharp on the store page. On the phone, the body is a two-column spread reduced to a gray stripe, and the "template" pages are screenshots of a desktop app. He cannot complete the first worksheet without putting the sandwich down and zooming. The author designed the file on a monitor. Diego is the reader.
Design the page for a hand, not for a spread
A phone does not show a letter-size page at a size you can read. The reader will zoom. Your job is to make zooming move down the page in one direction. One column does that. Two columns force the reader to pan sideways, lose the line, and guess which column comes next.
Pick a page size and stay with it. Letter or A4 is fine for a guide someone might also print. The margin is what keeps the line out of the curve of a thumb and out of the edge of a screenshot. Leave a generous margin on every side, including the side where a phone's scrollbar or notch can cover text. If a heading touches the edge on your export, the margin is too small. Fix the master page. Do not nudge one text box.
Headers and footers should be short. A running title is useful. A slogan, a social handle, and a full URL on every page eat the space the reader needed for the step. Page numbers help when someone says "the example on page 9." Put them where they are not the largest type on the page.
You might be thinking a landscape layout will feel more like a phone. A landscape page is wider, which usually means smaller type when the phone fits the width. Portrait, one column, is the safer default for a guide of steps. Save landscape for a single worksheet you have tested, not for the whole file.
Set type you can read at arm's length
Body text has to survive being viewed at a fraction of the page. There is no universal point size that fits every typeface. The test is whether you can read a full line on your own phone without zooming past the margin. If you cannot, increase the size or shorten the line. Do not solve it by telling the reader to pinch.
Use a plain typeface for the body. Decorative fonts that looked friendly on the cover become blobs at phone size. One family for headings and body is enough. Bold the heading. Do not signal structure with color alone. A reader in bright sun, or a reader who does not see the color the way you do, still needs the heading to look like a heading because of its weight and size.
Keep paragraphs short. A phone screen shows a few lines. A 200-word paragraph is a wall. Steps belong in a list with real numbers or bullets, not in a sentence that says "first, then, then, then." The list is easier to follow with a thumb.
Contrast is part of formatting, not a separate aesthetic. Dark gray on a tinted background often fails in a break room. Black or near-black text on white is the boring option that works. If you want a colored cover, keep the interior pages quiet.
The tool you use to lay this out is a separate choice. Canva versus InDesign compares speed and control. Either tool can produce a phone-readable file, and either tool can produce a poster that fails in Diego's hand. The settings matter more than the logo on the software.
Keep images from becoming the file
A guide full of full-page screenshots is heavy, and on a phone those screenshots are often unreadable because the text inside them does not scale as text. Prefer real text you typed. When you need a figure, crop it to the part the step is about, and write the instruction in the paragraph so the figure is an illustration, not the only copy of the words.
Export images at a size that looks clear on a screen, then check the PDF's file size. You do not need a print-resolution photograph for a guide nobody will put on a press. Large images are why a file stalls on a phone network and why a reader gives up before page two. If the export is slow to open on your phone, shrink the images and export again. Do not ask the reader to download over coffee-shop Wi-Fi as a test of commitment.
Avoid text baked into images for things the reader must do: prices, URLs, step numbers, form labels. If you later fix a label, you will regenerate the image and forget a page. Live text can be searched, and it can be read by the tools described in the accessibility guide.
Structure the file so a phone can move through it
A long guide without bookmarks is a scroll with no exits. Add a table of contents with links, and add bookmarks that match the headings. A reader on a bus should be able to jump to the worksheet, not scrub through forty pages of intro.
Reading order has to match the visual order. If you place a sidebar text box that the export writes first, a screen reader and some reflow tools will read the sidebar before the step. Keep the layout simple enough that the order is obvious. The W3C WAI standards overview is where the field describes structure, text alternatives, and how WCAG can apply to documents. Use it when you export. Do not treat a pretty page as a tagged page.
The fuller checklist for contrast, alt text, headings, and a screen reader pass is Accessibility Basics for PDF Guides. Read that article before you claim the file is accessible. This article will not repeat it. If you only do the phone test and skip tags, say nothing on the sales page about accessibility.
Run the lunch-break test
Export the PDF. Send it to your phone the way a buyer will get it, not through a desktop preview. Open it in the reader the phone uses by default. Try to complete one task from the guide with one hand. Diego's author should have tried to fill the first worksheet in the break room, not in the design app's presentation mode.
Watch for four failures. The type is too small. The columns make you pan. A step exists only inside a screenshot. The file takes long enough to open that you would abandon it. Fix those and export again. One clean pass is more useful than a new color palette.
Then check the sales page image. If the mockup shows a two-page spread and the file is a single column, the buyer is being shown a different product. Match the picture to the file. The launch checklist includes this phone pass on purpose. Do not skip it because the desktop export "looks done."
When the file passes in your hand, ask one more question: could you finish the first real task on a phone, in a loud room, without zooming past the edge of the page? If you could not, the formatting is not finished, no matter how the cover looks on a monitor.
FAQ
Should I ship a separate mobile PDF? Only if you cannot make one file readable. Two files mean two updates. A single column usually removes the need for a second version.
Is a web page better than a PDF for phones? Often, yes, for text that changes often. Buyers of a guide still expect a file they can keep. Format the PDF so the file is usable, and use the site for updates and the sales page.
What about fillable form fields? They can help if you test them on a phone. A field that works in desktop Acrobat and fails in a phone's preview is a broken worksheet. If you cannot test it, give a printable checklist of real text instead.
Do margins matter if the reader zooms? Yes. Zoom magnifies the edge as well as the type. A heading that starts at the trim will start off-screen or under a thumb.
Can I use a dark background to look modern? You can, if the text still meets a contrast you have checked and the file still prints for someone who wants paper. If you have not checked, use dark text on a light page.
Which app should I buy first? Start with the tool you will actually export from this week, then judge the file on a phone. The design comparison is there when you outgrow the first tool. The phone test does not wait for the upgrade.