Preparing a Framer export so your layout survives the conversion

Framer static export (HTML/CSS/JS)

Framer sites convert through the static pipeline. What you export is what you get, so publish the final version before exporting.

Quick answer

Publish your Framer site, then use the static export (or the published URL) — CONVERT2WP.NET converts the rendered HTML, CSS and JS into a WordPress theme.

Fidelity score 88–94Success rate 92%Framer static export (HTML/CSS/JS)

Where do I find the ZIP?

Publish the site first: Framer exports mirror the published version, not the editor
Open Project settings and locate the export/download option for your plan
If export is unavailable on your plan, paste the published Framer URL into the converter instead
Zip the exported folder without unpacking subfolders

What your upload should contain

index.html
Nested page folders with their own index.html
assets/ or static/ folder
CSS and JS bundles

Framer troubleshooting

Scroll animations behave differently

Framer's runtime drives complex scroll effects. Flatten them into CSS animations before exporting for the closest match.

CMS pages are missing

Draft CMS items are not exported. Publish every collection item you want in WordPress.

Fonts fall back to system fonts

Framer serves some fonts from its CDN. Upload custom fonts to the project so they are exported locally.

Best practices before exporting

Publish the site first — exports mirror the published version
Flatten heavy scroll effects that depend on the Framer runtime
Give every page a descriptive slug and SEO title in the page settings
Check that CMS collection pages are published, not draft

How to export

Method 1 — Static export ZIP (best result)

Open your Framer project and publish it
Go to Settings → Export and choose the static/HTML export option
Download the generated ZIP
Upload the ZIP directly to the converter

Method 2 — Published site URL

Copy the published Framer URL
Use the live website input in the converter
The crawler walks the navigation and sitemap and captures every reachable page

Method 3 — Manual HTML archive

Save the published pages as a static HTML folder
Keep the folder structure and asset paths intact
Zip the folder root (index.html must be at the top level or one folder deep)

Accepted input

ZIP archive
GitHub repository
Static export
Source project
Build output

Not recommended

Old build folders from a previous version of the project
Incomplete exports that are missing package.json or index.html
Screenshots, Figma files, PSD files or design mockups
node_modules — always exclude it, it makes uploads slow and adds nothing

Supported features

Static pages
Images and fonts
CSS animations
Navigation
SEO meta

Unsupported features

Framer CMS as live WordPress content
Framer forms backend
Interactive Framer components with runtime state

Common mistakes

Exporting a draft instead of the published version
Zipping a folder where index.html is buried several levels deep
Expecting Framer CMS to become WordPress custom post types automatically

Conversion tips

Simplify complex scroll animations before export — they translate to lighter CSS
Export at desktop and confirm mobile breakpoints in the preview

Readiness checklist

Navigation — Use real anchor links with readable labels. Menus built purely from JavaScript state are harder to map to WordPress menu locations.
Images — Reference images from your project folder (imports or /public). Images loaded from a temporary preview host may not be reachable at conversion time.
Assets — Fonts, icons and CSS should live inside the project. Locally hosted assets are copied into the theme automatically.
Forms — Standard form markup is converted to Contact Form 7 or WPForms. Custom JavaScript submit handlers are replaced by the WordPress form handler.
Routing — Every route you want as a WordPress page must be reachable from the navigation, a sitemap or a route manifest.
Animations — CSS animations and common libraries survive. Heavy scroll-timeline or canvas effects may render differently in WordPress.
SEO — Titles, meta descriptions and canonical tags are extracted per page and mapped into the theme and your SEO plugin.
Responsive — Breakpoints are preserved as-is. Check mobile before exporting — the converter never fixes a layout that was already broken.

Framer FAQ

How do I export from Framer?

Publish the site, then use Settings → Export to download a static HTML ZIP, or convert directly from the published URL.

Does Framer CMS transfer?

CMS pages convert as static pages. Rebuilding them as WordPress posts is a manual step after import.

Can I convert a Framer site without exporting?

Yes. Paste the published URL and the live-website pipeline crawls and converts the rendered pages.

Do Framer components convert?

They convert as rendered HTML and CSS. Interactive Framer code components lose their runtime behaviour.

Will my Framer CMS become WordPress posts?

Collection pages become WordPress pages by default. Ask us for a post-type mapping if you need them as posts.

Do I need to install anything to convert a Framer project?

No. Everything runs server-side. You upload a ZIP or paste a repository URL and receive a WordPress theme ZIP plus a live preview in the browser.

Should I remove node_modules before uploading?

Yes, always. node_modules is reinstalled during conversion, so including it only makes the upload slow and can push you over the size limit.

Can I preview the result before paying?

Yes. The WordPress preview is free for every conversion. Payment is only required when you download the theme ZIP.

What happens to my forms?

Standard HTML form markup is mapped to Contact Form 7 or WPForms shortcodes. Custom JavaScript submit handlers are replaced by the WordPress form handler.

Will my SEO titles and meta descriptions survive?

Yes. Titles, meta descriptions and canonical tags are extracted per page and written into the theme templates so your SEO plugin can take over.