Search for a WordPress PDF viewer and you get lists of plugins with feature tables. The tables rarely help, because the plugins are not competing at the same job. Choosing well means working out which job you have first.
This is a decision guide rather than a ranking. We make one of these plugins, and we have tried to be straight about where it is and is not the right answer.
Start here: what is the document for?
Four common situations, needing different tools.
A. A file people need to download
Forms, price lists, terms, manuals people keep. The reader wants the file, not an experience.
You probably need no plugin at all. A clear link with a file size and page count does the job. Adding a viewer here puts a layer between the reader and what they came for.
B. A document people read on the page
Reports, guides, whitepapers. You want readers to stay on your site rather than disappear into a downloads folder.
You need a straightforward embedder. Displays the document inline, scrolls, zooms. No page-turn animation required.
C. A visual publication people browse
Catalogs, magazines, brochures, lookbooks, menus. The layout carries the message and browsing is the point.
You need a flipbook viewer: page turns, spreads, thumbnails, clickable regions.
D. A document that is the product
Paid ebooks, member-only publications, course materials.
You need a viewer with access control that integrates with your membership or ecommerce plugin, plus previews and download controls.
Most disappointment comes from buying a category C tool for a category A problem, or vice versa.
The seven questions that decide it
1. How does it behave on a phone?
Ask this first. Check your analytics for the share of mobile traffic, then open the plugin’s demo on your own phone, not a narrowed desktop window.
What you want to see is a viewer that shows one page at a time on a narrow screen. A shrunk two-page spread on a phone is unreadable, and this is the most common reason readers give up.
2. Is the text real text?
Some viewers render each page as a flat image. It looks fine and costs you three things: readers cannot search the document, screen readers cannot read it, and search engines find no words to index.
Test it on a demo: try to select a sentence. If the whole page highlights as one block, it is an image.
3. Where is the file actually hosted?
Some WordPress plugins are front-ends for a hosted service: you upload to their servers and the plugin embeds an iframe.
That has consequences worth knowing before you commit. The content sits on their domain, so any search value goes to them. Your documents stay online only while the subscription runs. Some plans meter views. And if the service closes or changes pricing, every embedded document on your site is affected at once.
A genuinely self-hosted plugin keeps the file in your media library and renders it on your server. Ask directly. it is not always obvious from the plugin page.
4. What happens with your largest document?
Demos use small, well-optimised files. Your 200-page catalog with print-resolution photography behaves differently.
Test with your real worst-case file during any trial period. Ask about page limits and file size limits specifically: some tools have them and do not advertise them.
5. Does it fit how you build pages?
If your site runs Elementor, Divi, Avada, Bricks or WPBakery, check there is a native way to place the viewer rather than only a shortcode. Shortcodes work, but they cannot be previewed in the builder, which makes layout work tedious.
6. What does it cost over three years?
Compare like with like. Three shapes exist: a one-off purchase, an annual licence for updates and support, or a monthly subscription that also hosts your files.
Multiply by thirty-six months before comparing. Also check whether the features you need are in the base price or sold as separate addons: a low headline price with six paid addons is a different proposition.
7. What happens if you stop paying?
With a self-hosted plugin, it typically keeps working and stops receiving updates. With a hosted service, embedded documents usually go blank, including in every email and social post you have ever shared.
Find out which applies before you publish fifty documents.
Features that matter less than they appear
- Long feature lists. Twenty features you will never enable are not better than five you use daily.
- Page-turn realism. Pleasant, and rarely the reason a document succeeds or fails. Navigation and legibility matter more.
- Copy protection. Nothing displayed in a browser can be made uncopyable: screenshots exist. Controls are a deterrent, not a guarantee, and any vendor claiming otherwise is overselling. Personalised stamps on downloads, which make leaks traceable, are usually more effective than trying to block them.
- Install counts. A useful signal of maintenance, but a plugin with a million installs solving category B does not help with category C.
A sensible way to decide
- Identify your category: A, B, C or D above.
- Shortlist two or three plugins with a free version or trial in that category.
- Install them on a staging site and load your largest real document.
- Open each on your own phone.
- Try to select text on a page.
- Check the three-year cost and what happens if you stop paying.
Steps 3 and 4 eliminate most options quickly.
Where our plugin fits
To be direct about our own position: TNC FlipBook 3D is built for categories C and D: visual publications people browse, and documents you sell or restrict. It is self-hosted, keeps files in your media library, extracts page text so documents stay searchable and indexable, and integrates with the major page builders, WooCommerce and the common membership plugins.
If you are in category A, you do not need it, and a plain link is better. If you are in category B and only need a document to appear inline, a simpler embedder will do the job with less configuration.
There is a free version on WordPress.org, which is the right way to run the tests above before spending anything. Our comparison of WordPress flipbook plugins covers the category C options in more detail.
Things people discover after choosing
Five practical points that rarely appear on a feature list and reliably cause friction later.
The source file sits at a public URL
Uploading a PDF to the media library puts it at a predictable address. If your document is paid or restricted and the plugin does not protect that path, your access control is decorative. Anyone with the URL bypasses it, and search engines can index the raw file.
This is the most common oversight in the whole category, and it stays invisible until somebody finds it. Test it by opening the direct file URL in a private browser window while logged out.
Caching plugins and viewers disagree
Aggressive JavaScript optimisation, deferring or combining scripts can break a viewer that renders in the browser. The classic symptom is a document that works when you are logged in and fails for everyone else, because logged-in users usually bypass the cache.
It is fixable by excluding the plugin’s scripts from optimisation. Worth knowing before you conclude the plugin is broken and start again with a different one.
Updating a document without breaking links
Prices change and policies get revised. Check that you can replace the file while keeping the same page URL, rather than creating a new entry each time. If every update mints a new address, every link you have shared goes stale and any accumulated search value resets.
Migration is harder than installation
Moving between viewers usually means re-creating each document by hand. Worse, any shortcodes left in your posts render as visible text once the old plugin is deactivated, so readers see raw square brackets where a document used to be.
Search your content for the old shortcode before switching, do it on staging first, and expect the work to scale with how many documents you have published. This is the main reason to think about category fit at the start rather than after fifty documents.
Protection settings can break accessibility
Turning on copy protection can stop assistive technology reading a document at all. If you have accessibility obligations, check that your protection settings do not put you in breach, and treat any conformance claim as something to verify with an audit rather than accept from a feature list.
A ten-minute evaluation
Rather than comparing feature tables, run this against any shortlist. It settles most decisions faster than reading reviews.
- Identify your category: A, B, C or D above, and write down the three things the plugin must do. Ignore everything else on the sales page.
- Install the free version on a staging site and load your largest real document, not a sample.
- Open it on your own phone over mobile data. Time how long before anything appears, and try to read a paragraph without pinching.
- Try to select a sentence on a page. If the whole page highlights, it is images.
- Copy a link to page five and open it in a private window.
- Open the raw file URL while logged out and see whether it is reachable.
- Work out the three-year cost, and ask what happens to your documents if you stop paying.
Steps 2 and 3 eliminate most options on their own.
Frequently asked questions
Do I need a plugin to show a PDF in WordPress?
No. You can upload a PDF and link to it, and for documents people want to download that is the better option. A plugin is worth adding when you want readers to stay on your page.
What is the difference between a PDF viewer and a flipbook plugin?
A viewer displays the document, usually scrolling. A flipbook plugin presents it as a book with page turns, spreads and thumbnails. Viewers suit reading documents; flipbooks suit browsing visual publications.
Will a PDF viewer slow down my site?
The plugin’s own weight is usually small; your document is the heavy part. A large print-resolution PDF will be slow whatever displays it. Compress images to screen resolution and check that the viewer loads pages progressively rather than all at once.
Can search engines index a PDF shown through a plugin?
Only if the plugin renders the page text into your page. Flat-image rendering leaves no text, and plugins that embed from an external service place the content on that service’s domain.
Can I stop people downloading a PDF?
You can remove the download button and discourage casual copying, but anything visible on screen can be captured. Treat controls as a deterrent. For valuable documents, a personalised stamp on each download is generally more useful than an attempted block.
Is a free PDF viewer plugin good enough?
Often, yes, particularly for categories A and B. Paid versions tend to matter when you need access control, ecommerce integration, clickable regions or support. Start free and upgrade when you hit a real limit.
Why does my PDF work when logged in but not for visitors?
Usually caching. Logged-in users often bypass the cache, so a script optimisation that breaks the viewer only shows up for everyone else. Excluding the plugin’s scripts from JavaScript optimisation normally fixes it.
How do I move from one viewer to another?
Expect to re-create each document, and search your content for the old plugin’s shortcode first, since it will render as visible text once that plugin is deactivated. Do it on staging, and budget time in proportion to how many documents you have.
Can I restrict a document to logged-in users?
Yes, with a viewer that integrates with your membership or ecommerce plugin. Check as well that the source file itself is protected, because restricting the page while leaving the PDF at a public URL protects nothing.
