Framer is an exceptional design-and-publish platform. But if you're running an agency with 10, 15, or 20+ client sites, the per-site hosting fees don't stay invisible for long. That's not a criticism of Framer — it's just how the math works at scale.
This article breaks down exactly how one agency crossed the $1,200 savings threshold by exporting Framer sites and self-hosting them on their own infrastructure. It covers the real cost structure, the workflow, and the tradeoffs worth understanding before you do the same.
The Quick Answer
Self-hosting Framer sites via static export eliminates per-site hosting fees entirely. For an agency managing five or more client sites on paid Framer plans, that's a measurable saving from the first month — not a theoretical one. Export each site to HTML/CSS/JS, deploy to Cloudflare Pages or Netlify, and pay nothing per site for hosting.
Why Framer Hosting Costs Compound for Agencies
Framer's pricing model is sensible for individual designers or small teams: you pay for the platform, hosting is included, and everything is clean and simple.
For agencies, the math shifts. Each client site typically needs its own Framer plan, so you're not paying for one site — you're paying for an entire portfolio, each with its own recurring monthly fee.
Framer currently charges per site, not per account. In 2026, the main paid tiers are:
Basic — $10/month (annual billing), custom domain, 50 GB bandwidth, 2 CMS collections, 30 pages
Pro — $30/month (annual billing), 100 GB bandwidth, 10 CMS collections, staging, 150 pages
Scale — $100/month (annual billing), 200 GB bandwidth, 20 CMS collections, 300+ CDN locations, 300 pages
Most client-facing agency sites land on the Pro tier to access staging, site redirects, and the full CMS feature set. At $30/month per site, an agency managing 10 client sites is already spending $300/month — $3,600/year — just on hosting. Twenty sites brings that to $600/month or $7,200/year.
The "Made in Framer" watermark is a separate layer of cost that compounds the issue. It appears on every free-plan site, and removing it requires a paid plan — which is yet another line item on top of the hosting fees clients are already paying for.
How the Agency Restructured Its Hosting Stack
The agency in question managed 20+ client landing pages and marketing sites. Their goal was straightforward: keep designing in Framer, stop paying Framer's hosting fees for every client.
The solution was static export plus self-hosting.
Step 1: Export Each Site to Static HTML/CSS/JS
Using PullPage, they pasted each published Framer URL into the export tool and generated a static ZIP file containing HTML, CSS, JavaScript, and all bundled assets. Each export takes roughly 24 seconds.
The critical requirement was animation fidelity. Clients had approved designs with specific interactions, and a broken hover state on delivery is a support ticket waiting to happen. PullPage's export preserves Framer Motion animations, hover effects, and scroll transitions in the static output — that was non-negotiable.
Watermark removal happens automatically as part of the export process. No manual HTML editing, no post-processing scripts required.
Step 2: Deploy to Cloudflare Pages
Each exported ZIP was deployed to Cloudflare Pages. Cloudflare's free tier supports unlimited static sites with no per-site bandwidth charges — most marketing sites never approach the usage limits.
Netlify and Vercel work equally well. This agency chose Cloudflare Pages for the global CDN performance and zero-cost hosting at their scale.
Step 3: Configure GitHub Sync for Ongoing Updates
For sites needing regular content updates, they configured GitHub Sync through PullPage. When a client's Framer site changes, the designer re-exports, the commit goes to the repository, and the host redeploys automatically.
One developer on the team described the workflow: "I update the site, push to the repo, and let the host redeploy automatically." What could have been a manual, error-prone process became a repeatable CI/CD workflow.
The Cost Breakdown
Here's what the numbers look like before and after, using Framer's current 2026 pricing.
Before (Framer-hosted, 20 Pro sites):
Framer Pro plan per client site: $30/month (annual billing)
20 sites × $30 = $600/month
Annual cost: $7,200
After (self-hosted via PullPage):
PullPage Agency plan: covers unlimited exports
Cloudflare Pages hosting: $0 for static sites at this scale
Annual cost: PullPage subscription only
The $1,200+ figure in this article's title is actually a conservative floor — it reflects savings even for a smaller five-site portfolio after accounting for PullPage's subscription. At 20 Pro sites, the delta is closer to $7,000/year. For agencies with any clients on Framer's Scale plan ($100/month), the math becomes even more compelling.
It's also worth noting that the prices above are for annual billing. Month-to-month Framer pricing runs higher, so agencies that haven't locked into annual contracts are saving even more by moving off hosted plans.
What You Don't Lose by Self-Hosting
This is the question agencies actually ask: what breaks when you leave Framer's hosting?
The honest answer is less than you'd expect — if you export correctly.
What stays intact:
All Framer Motion animations and interactions
Hover effects and scroll transitions
Full CMS content across 100+ page sites
SEO settings, meta tags, and sitemaps
All local assets — images, fonts, videos, 3D models — bundled locally, not dependent on Framer's CDN
What you give up:
Framer's built-in CMS editing interface — changes require a re-export
Framer's native form handling — replace with a third-party service such as Tally or Typeform
Framer Analytics — replace with Google Analytics or Plausible (these are preserved through the export)
Framer Checkout and password-protected pages, which depend on Framer's servers
Automatic Framer platform updates — your static export is a snapshot of the live site at export time
For most agency client sites — marketing pages, portfolios, landing pages — these tradeoffs are entirely workable. The GitHub Sync workflow handles content updates cleanly. For sites with heavy real-time CMS editing by non-technical clients, self-hosting adds a step. That's worth knowing before you commit.
SEO Implications of Self-Hosting Framer Sites
A common concern is SEO continuity. The direct answer: self-hosted Framer sites can actually outperform Framer-hosted equivalents on Core Web Vitals, because you control the hosting infrastructure and asset delivery.
PullPage's export rewrites assets for optimized load times and generates functioning sitemaps. Deploying to Cloudflare Pages gives you edge caching and global CDN delivery without any additional configuration.
For a deeper look at the SEO side of Framer exports, the complete guide to improving SEO for Framer websites covers what to configure before and after export.
Is This Workflow Right for Your Agency?
It depends on your client mix and how frequently content changes.
Good fit:
Agencies managing 5+ client sites with relatively stable content
Designers delivering a clean, watermark-free static site to clients
Teams already using GitHub for deployment workflows
Clients on shared hosting or VPS who can't use Framer's hosting
Less ideal fit:
Sites where clients self-edit CMS content daily without developer involvement
Sites relying on Framer's native forms, password protection, or Framer Checkout
If you're unsure whether your sites qualify, the guide on exporting a Framer website in 2026 covers exactly what exports correctly and what doesn't. For a full breakdown of Framer's hosting tiers and how they scale, see the Framer hosting costs guide for 2026.
The Practical Checklist for Agencies
Here's the full workflow:
Publish each Framer site to a live Framer URL
Paste the URL into PullPage and generate the static export
Verify animations, interactions, and CMS content in the preview
Download the ZIP or configure GitHub Sync for the repository
Deploy to Cloudflare Pages, Netlify, or Vercel
Point the client's custom domain to the new host
Verify SEO settings, sitemap, and canonical tags post-deploy
Document the re-export process for the client's update workflow
Most agencies complete the first export in under 30 minutes.
FAQs
Does self-hosting break Framer animations? Not with a proper export tool. PullPage's rendering engine is built exclusively for Framer and captures Framer Motion effects, hover states, and scroll transitions in the static output. Generic web scrapers often miss these — a Framer-specific exporter handles them correctly.
What happens when the client wants to update their site? You update the design in Framer, re-export via PullPage, and redeploy. With GitHub Sync configured, the redeploy is automatic after the commit. For sites with frequent changes, this adds one step compared to Framer-hosted. That's the honest tradeoff.
Does the "Made in Framer" badge get removed automatically? Yes. PullPage strips the watermark, Framer editor scripts, and badge automatically as part of the export. No manual HTML editing required.
Can you self-host Framer CMS sites, not just single-page sites? Yes. PullPage supports full multi-page exports including CMS content. Paid plans handle 100+ page sites and exports over 500 MB.
What hosting platforms work with a Framer static export? Any platform that serves static files. Cloudflare Pages, Netlify, Vercel, and GitHub Pages all work. You can also deploy to a VPS or your own server — the export is standard HTML/CSS/JS with no Framer runtime dependencies.
Does SEO transfer correctly when you move off Framer hosting? Yes, if you export with SEO settings preserved. PullPage's paid plans maintain meta tags, canonical URLs, and generate sitemaps. Verify these after deploy and configure your DNS correctly to avoid any indexing gaps during the transition.
How long does an export take? Roughly 24 seconds for a standard site. Larger sites with extensive CMS content take longer, but the process is automated — you're not waiting manually.
How much does Framer charge per site in 2026? The current paid tiers are Basic at $10/month, Pro at $30/month, and Scale at $100/month — all at annual billing. Most professional client sites require Pro or higher to access staging, site redirects, and the full CMS feature set. See the Framer hosting costs breakdown for a full tier-by-tier comparison.
The math here is straightforward. If you're running an agency and paying Framer's per-site hosting fees across a client portfolio, self-hosting via static export is worth calculating against your current spend. Even at five Pro sites, you're paying $1,800/year for Framer hosting alone. PullPage is where that workflow starts.