PDFs are not ideal for e-book reading. They are useful for keeping a page’s shape, but that shape can make long reading hard on a screen.
A PDF is often a digital copy of a printed page. Its text sits in fixed blocks. The page may have two columns, wide margins, footnotes, page numbers, images, or a set type size. On a large screen, this can work well. On a phone or a small tablet, the reader may need to zoom in and move from side to side.
That is the first fact I want to keep clear. A PDF is made to show a page. An e-book format, such as EPUB, is usually made to let text adjust to the screen. The words can move into a new line when the window gets smaller. Readers can often change the type size, line spacing, and margins.
This process is called reflow. It means that text changes shape to fit the available space. Reflow helps when a reader enlarges the text or reads on a small screen. It also helps people who need a larger type size.
PDFs can support reflow in some cases. A well-made, tagged PDF can carry information about headings, reading order, tables, and images. A reading app may use that information to show the text in one column. The World Wide Web Consortium, or W3C, treats this as part of accessible document design.
That detail matters because “PDFs do not reflow” is too simple. Some do. Many do not reflow well. Some files are scans of paper pages. In those files, each page may be one large image. The words may look clear, but the computer may not know where one word ends or what order the text follows.
A scanned book may need optical character recognition, often called OCR. OCR turns an image of text into computer-readable words. It can help with searching and copying. It can also make errors. A letter may be read as another letter. A footnote may appear in the wrong place. A page number may enter the middle of a sentence.
These problems affect research as well as reading. A scholar may search a PDF for a name or phrase and get no result, even when the words appear on the page. The file may contain only images. Or the text layer may be incomplete. Search can also return a false match from a header, footer, or hidden text.
This is where the format question meets database literacy. A file is not only a container for a book. Its structure affects what readers can do with the book. It affects search, copying, quoting, screen-reader use, and note taking.
Fixed pages still have value. Page numbers help readers point to the same place. A printed edition may have a layout that matters. Art books, comics, maps, music scores, and books with complex tables may need a stable page view. A PDF can preserve that view better than a flowing text format.
The problem begins when a PDF is treated as a general e-book format. It may work well for a short article. It may work well when the reader needs to check a page image. It is often less comfortable for a book read from start to finish.
The reading app also matters. Different apps handle PDF features in different ways. A file may reflow in one program but keep its fixed page in another. Some apps offer reading modes that show one text column. These modes may leave out images, captions, page numbers, forms, or other parts of the page.
This creates an honest limit. The file name alone does not tell us enough. A PDF can be carefully built and accessible. Another PDF can be a poor scan with no useful text layer. A claim about the format must leave room for the file itself, the reading tool, and the reader’s needs.
In teaching, I would rather say this plainly than label one format good and another bad. PDF is a page format. EPUB is usually a flowing text format. Neither one fits every book or every task.
The difference becomes clear when the task changes. A reader who wants to compare page images may prefer PDF. A reader who wants to enlarge text and read for hours may prefer a format that reflows. A researcher who needs full-text search must also ask whether the file has real text, accurate OCR, and a usable reading order.
Reading order is the sequence in which content is presented. It can break in a PDF with columns, sidebars, or text boxes. A screen reader may read the right column before the left one. Copying text may produce a jumble. These are not small design flaws when the document is being studied closely.
The same issue appears in citations. A PDF may show page numbers that do not match the page numbers in a print edition. A database viewer may add its own screen pages. A scan may include blank pages or covers in its count. The stable page image helps, but it does not remove the need to check which numbering system is being used.
I am also cautious about calling a PDF an “e-book” without more detail. That label may describe a complete book, a chapter file, a scan, or a record with a link to another service. It does not tell us whether the text is searchable or whether the file will work well on a small screen.
For the Beyond Citation project, this is a useful teaching point. A database record can look simple while the attached file has important limits. The record may tell us the title, author, and date. It may not tell us if the file is image-only, tagged, searchable, or easy to reflow. Those details may be missing from public documentation.
The practical question is not only, “Can I open this PDF?” It is also, “What kind of reading does this file support?” Opening a file proves very little. A better check looks at text selection, search results, page order, zoom behavior, and the place of images and notes.
No single check settles the matter. A PDF can pass one test and fail another. It may have searchable text but poor reading order. It may have clear pages but no useful reflow. It may preserve a complex chart while making ordinary reading tiring.
That is why the headline needs to stay direct. PDFs are not ideal for e-book reading in many common cases, especially long reading on small screens. Their fixed page design often serves documents better than it serves books.
The exception is not rare enough to ignore. Good tagging and careful production can make a PDF much easier to read. Yet those features cannot be assumed from the file extension. The reader needs information about the actual file, and database records do not always provide it.
The Source List follows the same rule: one digital source worth knowing, one search tip, and one honest limitation. That last part matters here. A PDF may offer the book’s pages, while still falling short as a flexible reading format.