What's new
Every change you can notice, with the date it happened — including the quiet failures that took a while to find.
Toombler is built and maintained by one person, in the open. This page lists what changed and when — every change a user can notice, in plain terms. It is not a list of every commit; it is the ones that matter to someone using the thing.
Most entries are fixes rather than features, and that is on purpose. A flipbook viewer is the kind of software where the interesting failures are quiet ones: a book that renders but cuts off a page, a button that exists but never fires, a setting that saves but is ignored. Nothing errors, nobody reports it, and it can sit there for months. Several entries below are exactly that.
Found something behaving oddly? Tell us — a report of a quiet failure is worth more than a feature request.
- Flipbooks made by other people are no longer handed to search engines. A public flipbook page became indexable as soon as enough text could be read out of the PDF, which meant this site was asking Google to index a document we did not write and cannot vouch for, at our address. Public still means public: the page works, it can be shared, and it shows up in the gallery. We simply do not submit it any more.
- The manual has a flipbook edition, and that page now says something. It used to be a reader with a paragraph of boilerplate around it — 150 words, most of them the same on every flipbook page. It now explains what you are looking at, what to try in the reader, and what is deliberately not happening while you read.
- The Product Hunt and Open-Launch badges are gone from the footer. The Open-Launch one was an image fetched from their server on every page view — including on the privacy page itself — with a unique project id in the address, so your visit to this site was countable by someone else. That is the same thing we just removed twice over, so it goes too.
- Google Analytics and the Ahrefs measurement script have been removed from every page. Both counted visits that our hosting already counts — without cookies, and without a request to anyone else — so the only thing they added was a third party watching along. Nothing replaced them: what remains is that cookieless count, plus our own counters for how often a flipbook is opened and how far readers get.
- The privacy policy now describes what actually happens on two points where it promised more than the code does: there is no account to keep or close, and nobody has to be contacted to have something removed. What exists is a row per flipbook, which you delete yourself — and which deletes itself after twelve months unopened.
- The public flipbook page no longer loads a typeface from Google. It used the same font as everything else in practice, so the only thing that request added was your IP address arriving at Google on every visit. Nothing about how the page looks has changed.
- A flipbook now needs a title. The field said “Title (optional)” and quietly filled in “Untitled Flipbook” when it was left empty, which is exactly what ended up in the gallery, in browser tabs and in every shared link. Existing flipbooks keep whatever they are called.
- To save you typing it, the name of the PDF is offered as a suggestion once the link checks out — without the .pdf. It only fills an empty field, and you can type straight over it. Names like “document” or “download (3)” are skipped, because those are no better than no title at all.
- The plugin page now documents what the plugin actually does: the collapsible text version, how long it caches, what it adds to your site and what it leaves behind when you remove it.
- Tapping the side of a page turns it. On a touch screen only swiping worked before — a short tap did nothing at all, on any device, since the reader was first built.
- Guides for making a flipbook in German and Dutch, written for those readers rather than translated from the English one.
- The gallery explains what it is: why the list is short, what happens when you open an entry, and how to get your own flipbook listed.
- Search engines are now told when a page changed. They were not, which is why updated guides kept sitting in search results in their old form.
- The download button names the file after your flipbook instead of a random identifier.
- Links from a flipbook back to the site are tagged, so we can see which shared books actually bring readers.
- Search inside a document, as a setting you switch on per flipbook.
- The page text is now a real text layer over each page: selectable, copyable, and readable by a screen reader.
- The page-turn buttons sit against the book instead of floating, and move aside when the page counter is off.
- PDF rendering updated to pdf.js 6.3.289, which closes a security issue (CVE-2026-16633).
- A PIN is now checked on the server. Before, the check happened in the browser, which is the wrong place for a lock.
- The advertisement on the inside cover is marked as one and no longer sits beside a closed cover.
- The language switcher works for people who had already chosen a language once.
- Six more interface languages: Italian, Polish, Turkish, Indonesian, Japanese and Chinese — thirteen in total.
- The user manual is available in all thirteen.
- Statistics keep daily totals indefinitely, split by sign-in method and source, with a period selector.
- If your storage provider refuses a request, the viewer falls back to a copy kept for a week instead of failing.
- WordPress plugin 1.2.1, tested up to WordPress 7.1. Every plugin release is listed separately further down this page.
- Every use-case page now carries a live demo flipbook instead of a screenshot.
- PDF rendering moved to a local copy of pdf.js, so the reader no longer depends on an outside CDN being up.
- Ten long-form guides, and a Guides hub to find them.
- A flipbook shared on social media shows its own cover as the preview image.
- Pasting a bare file ID or a whole share message works; the link no longer has to be exactly right.
- Pinch to zoom, drag to pan and double-tap to zoom in the reader and in embeds.
- Borderless embeds, and a live preview of the embed in the settings panel.
WordPress plugin releases
The WordPress plugin is the one part of Toombler that lives on your own site, so it is the one part you update yourself. These are its releases, newest first, exactly as they appear in the plugin's own readme. They carry no dates: the plugin was kept outside this repository until September 2026, and a date we cannot verify is worse than none.
Version 1.3.1
- Fixed: the `brand` and `rtl` attributes were generated by the Toombler dashboard but not accepted by the plugin, so WordPress silently dropped them. A right-to-left book (Arabic, Hebrew, Persian) turned pages the wrong way, and a disabled "Powered by Toombler" badge reappeared. Both now work, and both are available as toggles in the block editor.
Version 1.3.0
- New: optional search box inside the flipbook. Enable it with the `search="1"` shortcode attribute or the "Search box" toggle in the block, and readers get a search field that finds text anywhere in the document and jumps to the page, with the match highlighted.
- Flipbook pages now carry an invisible text layer, so the text can be selected, copied and read by screen readers instead of being just an image.
- Both features run entirely in the reader's browser — no text is uploaded or stored.
- Scanned documents without a text layer are unaffected: the search box will simply find nothing.
Version 1.2.1
- Tested and confirmed compatible with WordPress 7.1.
- Readme and documentation housekeeping. No functional changes.
Version 1.2.0
- New: optional accessible text version. Enable it with the `text="1"` shortcode attribute or the "Show accessible text version" toggle in the block, and the plugin renders your flipbook's text as a collapsible block below the viewer — improving screen-reader access and search-engine indexing of your content on your own site.
- The text is fetched once from the Toombler API and cached locally (transient) for performance.
Version 1.1.1
- Removed the "Powered by Toombler" badge toggle from the plugin to comply with the WordPress.org plugin guidelines (no attribution links in plugin output).
Version 1.1.0
- Tested and confirmed compatible with WordPress 7.0.
- Flipbooks now load faster and show an instant cover preview while the document loads (delivered automatically through the Toombler viewer).
- Housekeeping and readme updates.
Version 1.0.3
- Full settings parity with the Toombler embed: every viewer option is now available via shortcode and the Gutenberg block.
- New: choose between two page-flip sounds (`flipsound`), and toggle the hard cover (`hardcover`).
- Added shortcode parameters: counter, flipsound, autoplay, autospeed, start, bookmark, zoom, drag, thumbs, duration, spine, borderless, adreplace, closed, hardcover, corners, mscroll.
- Block editor sidebar now exposes all viewer settings.
Version 1.0.2
- Updated block icon to the Toombler page-stack mark.
Version 1.0.1
- New Toombler brand icon (open book with fanned pages) for the Gutenberg block.
- Refreshed editor placeholder styling to match Toombler's branding.
Version 1.0.0
- Initial release — shortcode and Gutenberg block.
How updates reach you
There is nothing to install and nothing to update. The reader runs from our servers, so the next time anyone opens one of your flipbooks they get the current version, including the fixes above. Your embed code does not change and your links keep working.
The one exception is the WordPress plugin, which lives on your own site and updates like any other plugin, through the WordPress plugin screen.
Frequently asked questions
Do I have to update anything?
No. The reader runs from our servers, so the next time someone opens one of your flipbooks they get the current version. Your embed code and your links stay exactly as they are. The only thing you update yourself is the WordPress plugin, through the usual WordPress plugin screen.
Will an update break an existing flipbook?
It should not, and that is enforced rather than hoped for: the test suite keeps embed codes and file identifiers from earlier versions working, including the older identifier format from before 2026. If something does break, that is a bug and we want to hear about it.
Is every change listed here?
No — only the ones you can notice. Internal work, refactoring and test coverage are left out, otherwise this page would be a commit log rather than something you can read. If a change affects a button, a limit, a setting or a result, it belongs here.
Why are most entries fixes rather than features?
Because a flipbook viewer is the kind of software where the interesting failures are silent ones: a page that renders but is cut off, a tap that does nothing, a setting that saves but is ignored. Nothing errors and nobody reports it, so finding them is most of the work.
How do I report something that looks wrong?
Through the contact page. A description of what you did, what you expected and what happened instead is enough; a link to the flipbook helps a lot.