TL;DR — On March 23, 2026, Framer launched Static Files — a way to serve uploads from your Framer domain at paths you choose. Use it for domain verification,
/.well-knownmanifests, PDFs, and other assets that must live at a stable URL, managed next to Advanced Hosting with create, path edit, replace, and delete plus size, format, and path safeguards. If you previously chained redirects to fake root paths into/.well-known/…, Framer says that workaround is no longer necessary.
This yoframer guide lives at /framer-updates/framer-static-files-hosting-update/ and translates Framer’s Static Files announcement for founders, agencies, and SEO or platform integrators who need non-page assets on the same domain as the marketing site.
Static files at a glance
| Area | What Framer shipped | Why it matters day to day |
|---|---|---|
| Hosting | Files served from your Framer domain at custom paths | Verification, compliance, and partner files live beside the site without a separate CDN bucket |
| Operations | Full lifecycle in the dashboard Files tab | Add, retarget paths, replace binaries, and delete without redeploying canvas pages |
| Safety | Size limits, format checks, path validation | Fewer accidental collisions and unsupported uploads breaking production |
| Migration | Retire redirect hacks for /.well-known/… | Cleaner DNS and redirect tables; fewer “why is Search Console failing?” threads |
| Plans | Included on Pro and Scale (Help also lists Enterprise) | Know before you promise a client that apple-app-site-association will “just work” on a free sandbox |
What Framer Static Files change
1. Non-page assets get a first-class home
Framer sites are excellent at designed pages and CMS-driven routes, but real launches also need robots.txt tweaks, llms.txt for AI crawlers, PDF spec sheets, and platform verification files. Static Files treat those as hosted assets with explicit paths — not as improvised redirects or mystery pages hidden off-menu.
2. Paths are deliberate, not accidental
Framer’s help workflow separates upload from path: you set the directory (for example /pdfs or /.well-known) and the file name appends automatically. That matches how operators think — “this JSON must live at /.well-known/assetlinks.json” — instead of guessing which canvas slug might collide.
3. Safeguards reduce production foot-guns
The release highlights size limits, supported format checks, and path validation. For agencies, that is the difference between a junior uploading a 200 MB build artifact to production and getting a clear rejection before publish.
4. Redirect workarounds can come out of the playbook
Framer explicitly calls out teams that used redirects to point root paths at /.well-known/… locations. Static Files are meant to serve the file at the real URL, which simplifies Search Console, Apple Pay domain association, and Android App Links setups that break when an extra hop goes missing.
How to upload and publish a static file
Framer documents the flow in Static files help. Condensed for a first pass:
- Open the site dashboard and select your domain in the sidebar.
- Open the Files tab (alongside other Advanced Hosting settings).
- Click + and upload the binary.
- Set the path — the folder segment only (for
example.com/pdfs/guide.pdf, use/pdfs, not the filename). - Publish the site so the URL goes live on your domain.
Supported categories (from Framer Help) include common text (PDF, TXT, CSV, JSON, XML, MD), images, audio and video, and archives — with a note to contact Framer if you need an unlisted extension.
Three workflow recipes to try this week
Search Console verification without redirects
You are launching a Framer site on a custom domain and Google Search Console wants a root or .well-known file at an exact URL.
- Upload the verification file Framer or Google provides and set the path to match the required URL (for example /.well-known/google-site-verification.txt).
- Publish once, then fetch the URL in an incognito window before clicking Verify in Search Console.
- Remove any legacy redirect rules that used to point a fake root path into /.well-known — Static Files should make them redundant.
Ship llms.txt for AI discovery
Your marketing site should explain itself to LLM crawlers without stuffing machine-readable copy into the hero.
- Draft llms.txt with allowed paths, contact, and positioning — keep it factual, not keyword-stuffed.
- Upload with path /llms.txt so it resolves at yourdomain.com/llms.txt.
- Link to it from the site footer or docs only if humans need it; the win is crawler-facing clarity.
Mobile deep links and wallet verification
The product team needs apple-app-site-association or Android assetlinks.json on the same domain as the Framer marketing site.
- Confirm the client site is on Pro, Scale, or Enterprise before promising Static Files.
- Upload each JSON to the exact /.well-known path the platform documents — no canvas page stand-ins.
- Coordinate with app release timing: publish Framer, then run Apple or Google validation tools the same day.
Framer templates for hosting-heavy sites
These remix-friendly files give you realistic site depth while you test domain settings — useful when Static Files sit next to CMS blogs, docs PDFs, or partner verification.
Revior — SaaS marketing with room for docs and verification
by OneFramer
Revior is a credible default when you want a production-shaped SaaS homepage plus CMS blog rows — the kind of project where Static Files often appear right after the first custom domain goes live.
- Best for
- Teams pairing a launch site with downloadable specs or Search Console on a custom domain
Bizent — Multi-page corporate presence
by OneFramer
Bizent’s multi-collection structure mirrors messy real clients — a good sandbox to document which paths are Static Files versus CMS routes before handoff.
- Best for
- Agencies handing off a domain with policies, PDFs, and platform files
Write — Editorial blog and content hub
by Charu
Write keeps the story content-forward — ideal if you are testing llms.txt or IndexNow keys without rebuilding the entire marketing narrative.
- Best for
- Publishers who may add llms.txt or IndexNow files beside a CMS blog
Browse more starting points in the template directory or our Framer updates hub.
Official Framer resources worth bookmarking
- Static Files release notes — canonical announcement (March 23, 2026).
- Static files help article — upload steps, MIME behavior, and common paths.
- Framer hosting overview — how publishing and domains fit together.
- Framer pricing — plan limits that affect file counts and hosting features.
- All Framer updates — adjacent releases including CMS 3.0 and CMS Plugins.
More reading on yoframer
- Framer updates hub — editorial coverage of platform releases.
- Framer CMS 3.0 deep dive — when your team lives in collections as much as hosting settings.
- Submit a template or tool — if you ship a hosting checklist or verification kit for Framer agencies.
The bottom line
Static Files close a long-standing gap: Framer domains can now serve the auxiliary files operators expect — verification, manifests, PDFs, and /.well-known JSON — without redirect gymnastics. If you are on Pro, Scale, or Enterprise, schedule one staging publish to upload, hit the public URL, and fold the path list into your launch runbook.
