Skip to main content
FXFramExporter
Export a site
Migration path

Framer to WordPress

The most widely deployed CMS on the web, built around themes, plugins, and a PHP-rendered admin.

VerdictPartial path
Read this before you quote the work
A static export is not a WordPress theme, and anyone promising a one-click conversion is selling you a wrapper. What the export gives you is the finished markup and CSS — the exact thing a developer needs to build the theme from, without rebuilding the design from a screenshot.

The order that works

  1. 1Export the published Framer site so you have the rendered HTML, CSS, and assets.
  2. 2Install a blank starter theme (Underscores or a block-theme starter) in wp-content/themes.
  3. 3Move the export's CSS and asset folders into the theme directory and enqueue them from functions.php.
  4. 4Split the exported HTML: header markup into header.php, footer into footer.php, the body of the homepage into front-page.php.
  5. 5Replace repeated content — posts, team members, case studies — with WP_Query loops so the client can edit them.
  6. 6Point the domain at WordPress only after the theme renders correctly on a staging subdomain.

What you keep

  • Exact visual design, including breakpoints
  • CSS animations and transitions
  • Optimised image assets
  • Copy and page structure

What you rebuild

  • Framer's interaction runtime — scroll-linked effects need rebuilding in CSS or JS
  • Framer CMS bindings, which become WordPress loops
  • Framer form submissions, which move to a WordPress form plugin
The mistake to avoid
Dropping the whole export into a folder and iframing it from a WordPress page. It renders, and it destroys the site: the CMS controls none of the content, and search engines see a nearly empty parent document wrapping a frame.

Questions

›Can I import a Framer site directly into WordPress?

A static export is not a WordPress theme, and anyone promising a one-click conversion is selling you a wrapper. What the export gives you is the finished markup and CSS — the exact thing a developer needs to build the theme from, without rebuilding the design from a screenshot.

›What transfers from Framer to WordPress?

Exact visual design, including breakpoints. CSS animations and transitions. Optimised image assets. Copy and page structure.

›What has to be rebuilt?

Framer's interaction runtime — scroll-linked effects need rebuilding in CSS or JS. Framer CMS bindings, which become WordPress loops. Framer form submissions, which move to a WordPress form plugin.

›What is the most common mistake on this migration?

Dropping the whole export into a folder and iframing it from a WordPress page. It renders, and it destroys the site: the CMS controls none of the content, and search engines see a nearly empty parent document wrapping a frame.