PDFs follow deployments
PDFs are stored with the release that references them, which keeps downloadable assets consistent after rollback.
Features
Upload PDF files as static assets inside your site and link to them from pages, buttons, forms, or documentation.
PDFs are stored with the release that references them, which keeps downloadable assets consistent after rollback.
StaticX hosts static public websites. Do not upload private or sensitive PDFs unless they are meant to be publicly accessible.
Upload the PDF into your file tree, link to its path, then publish a version when the change is ready.
Use PDFs for public downloads, menus, brochures, terms, reports, or lead magnets that belong to the site release.
Upload the file into a clear folder such as downloads or assets/documents.
Reference the PDF from a button, navigation link, landing section, or documentation page.
Create a deployment version so the PDF and the page linking to it stay in sync.
A PDF link can be just as important as the page around it. If a brochure, contract, menu, or report changes, teams need to know which file was live at the same time as the HTML.
StaticX stores PDFs with the site files so rollback restores both the link and the asset, avoiding mismatched downloads after a release change.
Static assets can be requested directly. Do not upload private PDFs unless they are meant to be public.
Changing a PDF filename changes the public URL, so update all page links before publishing.
Large PDFs count toward storage and can slow visitor downloads. Compress where possible.
Short, practical answers for using this page safely.
Yes. Upload PDFs as static assets and link to them from your HTML pages.
No. Files in a public static site should be treated as public. Use another storage model for private documents.
Yes, after you publish a deployment version containing the PDF change.