Download HTML Flipbook: A Self-Hosting Guide

To download an HTML flipbook from FreeFlipbook, open your completed publication and select Download HTML Version. The button saves a ZIP with the reader, CSS, JavaScript and page images, ready to extract and host on your own website. Keep the files together: downloading an HTML document alone is not enough to make the publication independent of its original server.

This guide is for publishers, teachers and website owners who want a catalog, brochure or lesson to live at their own URL. If you have not created a publication yet, start with our PDF-to-flipbook walkthrough or upload your PDF.

What is inside the HTML download?

The ZIP is a static publication, rather than a copy of the FreeFlipbook application. The export rebuilds the current reader from the stored publication settings and packages its required assets. It does not include a database, an editor or a server-side conversion service.

index.html
README.txt
logo.svg
pages/       # numbered page images; optional source PDF
flipbook/    # viewer JavaScript, CSS, controls, backgrounds and audio
assets/      # localized background and company logo, when present

The reader uses relative asset paths, so the same folder can live at a domain root or below a path such as /catalogs/spring/. Those paths are the main difference from the old single-file download: the publication no longer needs to load its page images from the original FreeFlipbook file server.

The package keeps the page-turning reader, navigation and configured visual settings. Google Fonts requests are removed and system fallback fonts are used. Hosted ads, analytics and the external social-sharing widget are excluded; copying the page URL and following ordinary website links remain available.

How to download HTML flipbook files

1. Finish the PDF upload and wait until the publication is available to read.
2. Open its result page using the original upload browser or your owner account. Knowing a public reading URL alone does not grant export access.
3. Select Download HTML Version. If a Save File dialog opens, choose a destination ending in .zip.
4. Wait for the packaging progress to finish. Leave the tab open while the browser downloads the required assets.
5. Extract the complete archive to a new folder before previewing or deploying it.

There is no separate export checkout in this workflow. The publication must still be available, and normal plan and hosting limits apply to the hosted source. The PDF itself is packaged only when the publication's PDF-download entitlement and setting both allow it; page images are sufficient for the interactive reader.

For large documents, use a supported desktop browser with the Save File picker so the archive can be written progressively to disk. Without that capability, the fallback holds the archive in memory and stops above 512 MiB. This exporter produces standard ZIP files below 4 GiB, rather than ZIP64 archives.

Preview the extracted HTML locally

Start with a local HTTP preview before uploading anything to a host. A double-click opens a file:// URL, where browser security rules can differ from a real website. An HTTP preview makes missing paths and asset errors easier to diagnose.

Example 1: a local preview command

Open a terminal inside the extracted folder and run this command with Python 3 installed:

python -m http.server 8000 --bind 127.0.0.1

Open http://localhost:8000/, then test the first, middle and last pages. The command serves the current folder locally; it does not publish your files to the Internet. Python's official HTTP server documentation describes the command and warns that this server is unsuitable for production.

After the first load, disconnect from the network and reload the local preview to check the packaged reader. Page images and controls should remain available from your local server. Links to other websites will naturally need a connection, and a local preview URL is not a public share link.

Deploy the downloaded HTML to your website

The reader needs a host that serves static files. Choose based on your current publishing workflow, access requirements and file sizes, rather than on the page-turning effect. Check the host's current storage, upload and usage limits before choosing a plan.

Cloudflare Pages

For an upload-based workflow, create a Pages project using Direct Upload and provide the extracted site assets. Keep index.html at the top level of the uploaded site, with its sibling directories alongside it. Cloudflare's Direct Upload guide documents folder and ZIP uploads and their restrictions.

This package is already built: it does not need a Next.js build command or the FreeFlipbook application's D1 and R2 bindings. Open the deployed address and inspect the entire publication before attaching a custom domain. If a file exceeds the host's limit, choose a suitable host or reduce the source document rather than omitting that file.

GitHub Pages

Place the extracted files in the repository directory configured as your Pages publishing source. Ensure index.html is at that directory's top level, then follow GitHub's site creation instructions. The relative paths are useful for project sites served below a repository name.

Review the repository and site's visibility before publishing. A static flipbook is not a protected document portal, and putting private materials in a public repository exposes the underlying files. No GitHub-specific build step is part of the export.

An existing website or web server

Create a folder such as catalogs/spring beneath your web root and upload the extracted contents there. The resulting address might be https://www.example.com/catalogs/spring/. Preserve filename case: a case mismatch that goes unnoticed locally can fail on a Linux host.

Use the self-hosted flipbook in a page

You can link directly to the hosted directory or place the reader inside an iframe. Use the URL of your deployed copy when independence from FreeFlipbook hosting is the goal. Our flipbook embedding guide explains the broader website workflow.

Example 2: a responsive iframe

<iframe
  src="https://www.example.com/catalogs/spring/"
  title="Spring product catalog"
  style="width:100%;height:80vh;border:0"
  loading="lazy"
  allowfullscreen>
</iframe>

Replace the example URL with your deployed reader address. Give the frame a useful title and enough height to show the controls. If the host blocks framing through security headers, adjust that host's configuration or share a direct link instead.

Example 3: a regular download-page link

<a href="/catalogs/spring/">Read our spring catalog</a>

A normal link is often the best choice for email, mobile navigation or an existing product page. Add a short text summary near it so visitors know what the publication contains before opening the reader. Avoid putting the private management link in that page.

Troubleshoot an incomplete export or deployment

If packaging reports a missing asset, the export stops instead of silently delivering an incomplete reader. Confirm that the hosted source publication still opens, then retry from the original upload browser or the owner's session. An expired, deleted or unfinished publication cannot be exported through this endpoint.

Custom backgrounds and logos can introduce another download restriction. The image server must allow cross-origin browser requests; an image being visible in an ordinary browser tab does not prove that JavaScript can download it. Use a suitable directly downloadable image or select a built-in asset before exporting again.

If the ZIP extracts but the deployed page is blank, check the browser Network panel for failed scripts and stylesheets. An HTML error page returned for a JavaScript URL is a hosting-path problem, not a successful script download. Keep the folder layout intact and verify that the host is serving the actual extracted files.

When only pages are missing, inspect requests under pages/ and verify that every numbered image was uploaded. When the background is wrong, check assets/ and the CSS background files. Test a fresh browser tab after updating the deployment so an older cache does not hide a missing file.

Updates, privacy and search visibility

The download is a snapshot, not a synchronized publication. Changes made later in FreeFlipbook do not reach the exported folder automatically. Export again and replace the deployed package as a unit so HTML, scripts and images remain consistent.

Deleting the original hosted publication does not delete a copy you already downloaded or deployed elsewhere. Your host controls that copy's availability and access. For private documents, use appropriate host-level access controls; hiding the reader URL is not an access-control system.

The exported reader keeps its noindex, nofollow metadata and represents PDF pages as images. Do not expect those page images alone to provide searchable article text. If discovery matters, publish an indexable landing page with an accurate summary, useful headings and a descriptive link to the reader, alongside your usual sitemap and canonical setup.

This documentation describes the export implementation and its supported file structure; it does not claim that every hosting provider or browser has been tested. Before sharing a production URL, verify navigation, fullscreen, page-turn audio where allowed, custom imagery and the optional PDF link on your target devices. Browser autoplay and fullscreen permissions can still require a reader gesture.

Ready to download an HTML flipbook? Create your publication, finish any customization, then export its ZIP and deploy the extracted folder. For the choice between a hosted link and a self-hosted reader, start with our HTML5 flipbook overview; keep the README with the archive so the next person can deploy it without guessing.