FAQ

Frequently asked questions

Quick answers to the questions we hear most from educators evaluating HTML5 flipbooks.

Are the templates really free?

Yes. Every template is open source under a permissive license. You can use them in classrooms, in commercial training, and in publicly available courses without paying us anything.

Do I need to credit PageFlip Guide?

No. The templates belong to their original authors and PageFlip Guide just makes them easier to find. Crediting the original repository is appreciated where the license requests it.

Can I use them inside Moodle, Canvas, or Google Classroom?

Yes. The standard pattern is to publish the flipbook to any static host (GitHub Pages, Netlify, your school server) and embed it via an iframe on the LMS page.

Do they work offline?

Most templates are pure static HTML and CSS, which means they work fine when opened from a USB stick, a folder on a Chromebook, or a Raspberry Pi running a tiny static server.

Are they accessible to screen readers?

Templates that ship with a text layer underneath the page image and proper landmarks are accessible. Our accessibility tutorial covers a checklist for verifying this on any starter.

What about analytics?

You can wire any flipbook to a small custom endpoint to capture page-flip events. We recommend keeping analytics minimal and transparent rather than installing a heavy commercial tracker.

Is there a hosted SaaS version?

No, by design. PageFlip Guide is a reference library, not a hosted service. You retain full control over where the flipbook is published and who can see it.

How is the gallery kept up to date?

We re-run the seeding script monthly to pull fresh repositories from the GitHub Search API and merge them with curated suggestions from readers.

Can I contribute a template?

Absolutely. Send us the GitHub link via the contact page and we will review it for the next refresh cycle.

What languages are the templates in?

Most are in English with some bilingual examples. Because the templates are static HTML, swapping the content language is usually a single search-and-replace away.