E-Paper for TYPO3

Most e-paper solutions in TYPO3 are Flash successors, and that is exactly how they feel

E-paper extensions for TYPO3 conceptually date back to the Flash era: a PDF is uploaded, and a JavaScript library simulates page turning with a 3D animation. At first glance, that looks impressive. At second glance: not indexable (Google cannot read the content), not responsive (a disaster on smartphones), not accessible, and with load times beyond 5 seconds. There are better ways to present magazines and catalogs in TYPO3.

The key question is not “Which e-paper plugin?” but “Do we need an e-paper at all?” In most cases, the answer is no. The content belongs on the website as HTML, not as a PDF inside a page-flip catalog.

Typical use cases

Corporate magazines and customer publications. Marketing departments produce quarterly print magazines and want to offer the digital version on the website. The classic approach: upload the PDF and embed a page-flip widget. The better approach: publish the articles as individual TYPO3 pages (via tx_news), with a magazine overview page as the hub. Every article can then be indexed, linked and shared on its own. The PDF remains available as a download for offline readers.

Product catalogs for trade partners. Wholesalers and B2B companies provide product catalogs to their dealers. The catalog data often exists as an InDesign export (PDF). An e-paper widget makes the catalog browsable, but not searchable. The better route: maintain the product data in a structured way in TYPO3 and present the catalog as a filterable, searchable HTML page. The PDF serves as the print version for download.

Annual reports and sustainability reports. Listed companies publish annual reports that have to match the print layout visually. Here, a PDF-based viewer is justifiable, because the layout is binding and individual pages require exact page breaks. Even so, the core data (financial figures, management statements) should also be available as HTML.

Technical architecture

E-paper solutions in TYPO3 fall into three categories:

PDF-based page-flip catalogs. A PDF is uploaded, and a JavaScript library (Turn.js, FlipBook.js, pdf.js) renders the pages in the browser. The library splits the PDF into individual pages and displays them as canvas elements. Pros: quick setup, and the layout matches the print version one-to-one. Cons: no SEO value (the content is hidden inside the PDF), poor performance with large PDFs (50+ pages), no responsiveness.

HTML-based magazine layouts. The articles are maintained as regular TYPO3 content elements and displayed through a magazine template. The layout recreates a magazine aesthetic (full-bleed images, text columns, pull quotes) using CSS Grid and Tailwind. Pros: full SEO indexing, responsive, fast, largely accessible. Cons: higher initial effort, and the layout deviates from print.

Hybrid approach. The articles exist as HTML, and a PDF download is offered in addition. On the overview page, visitors see article teasers, with the PDF of the complete magazine available for download in the sidebar. This approach combines SEO value with print fidelity.

For PDF display in TYPO3, pdf.js (Mozilla) is a good fit: an open-source library that renders PDFs natively in the browser. pdf.js performs better than Turn.js-based page-flip catalogs, does without page-turning animations and instead offers a clean, scrollable view with zoom and text search.

Common problems and solutions

PDF load time over 5 seconds. A 40-page magazine PDF weighs 20-40 MB. Without optimization, the browser downloads the entire PDF before it shows the first page. The fix: pdf.js supports byte-range requests, which load only the requested page. The server must support Accept-Ranges: bytes. In addition, optimize the PDF for the web with Ghostscript or qpdf (linearize) so that the first page appears immediately.

Content not indexed by Google. Google crawls PDFs and indexes their text, but not inside a JavaScript viewer. If the PDF is only rendered through a canvas element in the browser, Google sees no content. The fix: present the content as native HTML elements and also link the PDF as a download, because Google indexes linked PDFs directly. Hidden text meant only for the search engine is not an option: it violates Google’s spam policies, and aria-hidden hides text from screen readers in the first place.

Outdated page-flip libraries. Many e-paper extensions rely on libraries that have not been updated in years: Turn.js (last update 2013), FlipBook jQuery (jQuery dependency) or commercial libraries with expiring licenses. The fix: migrate to pdf.js or an HTML-based presentation. Both are future-proof and independent of third-party licenses.

Migration and version compatibility

The e-paper extensions in the TER are mostly outdated. Most of them support TYPO3 v10 or v11 at best. For v12 and v13, there are no maintained page-flip extensions.

The recommended route for TYPO3 v12/v13: for PDF-based presentation, embed pdf.js as a standalone library (no extension needed). For HTML-based magazines, use tx_news with a magazine template and a dedicated “Issues” category. A custom magazine layout based on tx_news takes 3-5 days.

If you are migrating from an existing e-paper extension, you have three options: pdf.js integration (1-2 days, keeps the PDF-based model), HTML migration (5-10 days, moves the content into tx_news articles) or an external service (Issuu, Yumpu) embedded in TYPO3. Gosign recommends the HTML approach for maximum SEO value and advises on the choice between the options.