Once you've converted a Framer site, Vercel is one of the simplest places to actually put it live โ here's the real step-by-step, for both export types.
If you exported to Next.js
- Push the exported project to a GitHub repository (or use a one-click deploy flow if your converter offers it).
- In Vercel, "Add New Project" and import that repository. Vercel auto-detects Next.js and sets the build command (
next build) and output correctly โ no config needed for a standard export. - Add your custom domain under Project Settings โ Domains, and point your DNS (an A/CNAME record, depending on whether it's an apex domain or subdomain) at Vercel's values.
- Deploy. Every future push to your main branch redeploys automatically.
If you exported to static HTML
Static HTML doesn't need a build step at all โ it's arguably even simpler:
- In Vercel, choose "Deploy" and either connect the repo or drag-and-drop the exported folder if your converter's dashboard supports a direct static deploy.
- Set the framework preset to "Other" (no build command needed) if importing via Git.
- Domain setup is identical to the Next.js path above.
What to actually check after deploying
- Every route resolves โ click through your site's full nav, not just the homepage. Multi-page Framer sites sometimes miss a route if the exporter's page-discovery didn't crawl everything.
- Images load from your own domain, not still pointing at
framerusercontent.comโ a partial export can leave some image references unrewritten. - Forms actually submit โ see our guide on Framer forms after export; this is the single most commonly missed step.
- Run a fresh Lighthouse audit on the live Vercel URL, not just a local preview โ real CDN edge performance differs from local.
- Check your canonical URLs and sitemap point at your new domain, not the original Framer subdomain, if SEO continuity matters to you.
Check the plan before you go live: Vercel's Hobby plan is free, but its docs say it "restricts users to non-commercial, personal use only," so a business site needs the paid Pro plan. The point of exporting off Framer's hosting is usually cost and control, and Vercel delivers the control without a steep learning curve.
Related conversion check
Generate the Next.js project from your published Framer URL, then deploy to a preview URL first. Check nested routes and forms there before pointing the production domain at Vercel.
Starting a new site instead? FNJ's AI website builder designs one from a description and a site you like, then gives you the code to host anywhere.