Verifying Framer site ownership

For the 1-credit verified-download option, Deframer verifies ownership by asking you to publish a one-line meta tag, <meta name="deframer-verification" content="dfv_…">, on your Framer site. Converting is free for an unprotected published Framer site; the check comes when you download the code. You paste the tag into Site Settings, then Custom Code in Framer, publish, and click Check again; the download unlocks once the code is found on the live page. Only someone who can publish the site can add the tag, which makes it a simple proof of control. It is checked before each new verified download. You may instead choose a 10-credit direct download and explicitly confirm ownership or permission. Neither option bypasses an active site-protection registration.

Why verification exists

Deframer converts published Framer sites into Next.js projects by reading the public files they serve. Those files are public, but the design and content in them belong to the site's owner. Deframer is for your own sites, or sites whose owner has given you permission, and the verified-download option checks publishing access as described in the terms.

A meta tag works well as proof because it sits behind the one permission that matters: publishing. Anyone can view a site, but only its owner, or someone the owner trusts with the project, can change its custom code and publish it. If your code appears on the live page, you control the site.

Deframer is an independent tool, not affiliated with Framer. It doesn't use your Framer login or need any access to your Framer account; the published page is the only thing it checks.

How your code works

• It's personal. Each Deframer account has one code: dfv_ followed by 24 characters.
• It covers all your sites. You use the same code on every site you download.
• It is checked before every new verified download. Removing it stops the 1-credit verification route. Direct downloads remain available with explicit permission confirmation unless site protection is active.
• Only your code counts. Someone else's code on your site doesn't let you download it, and yours doesn't let them.
• It never ships in your project. The converter strips the verification tag from the converted code.

How to add the tag, step by step

1. Sign in to Deframer, convert your site and choose to download it. Use the address visitors open (a *.framer.website, *.framer.app or custom domain), not the editor link.
2. Copy the meta tag Deframer shows. Copy the whole line; a partial code won't match.
3. Open your project in Framer and go to Site Settings, then Custom Code.
4. Paste the tag at the end of the <head> section. The check requires the tag in the head; body content does not count.
5. Publish the site. Custom code changes reach the live page only after you publish.
6. Return to Deframer and click Check again. When the code is found, Deframer shows that ownership is verified and the download unlocks: the first download of a project uses one credit.

The result looks like this in your site's head:

<meta name="deframer-verification" content="dfv_…">

The rest of the flow is in how to export a Framer site to Next.js.

Troubleshooting: the code isn't found

If Check again doesn't find the code, work through these in order.

Did you publish?

This is the most common cause. Saving custom code in Framer isn't enough; the change has to be published. Publish, then check again.

Is it on the right site and page?

• Make sure you pasted the code into the project that serves the URL you entered in Deframer, not a copy or a staging project.
• Use site-wide custom code. If you added the tag to one page's custom code only, it won't appear on other pages, including the one you pasted.
• If you use a custom domain, check the same address you gave Deframer. Open it in your browser, view the page source, and search for deframer-verification.

Is the whole code there?

Compare the code in your page source with the one Deframer shows, character by character if needed. A truncated or edited code doesn't match. If you have more than one Deframer account, make sure you copied the code for the account you're signed in with.

Is the published page updated yet?

Deframer fetches the page fresh when it checks, but give a new publish a moment to go live, then click Check again. If your page source in the browser still shows the old version, wait and reload before checking again.

Is it actually a published Framer site?

If you see "Not a published Framer site" instead, the address doesn't serve a published Framer page. Check that you used the live site address, not the editor link. Other messages are covered in common Framer to Next.js conversion issues.

Removing the tag after converting

The tag is only needed while you unlock a download. Once you have your download, you can remove it from Framer's custom code and publish again. The converted project never contained it, because the converter strips it.

Keep in mind that the code is checked before each new project is downloaded. If you remove it and later want to download a new conversion of the site, for example after a redesign, add it back, publish, and check again.

Agencies and client sites

An agency downloads a client's site once the client publishes the agency's code on it. That publish demonstrates the client has allowed your account to verify the site. Removing the tag stops further verified unlocks; an active protection registration blocks both download routes.

A clean way to handle it:

1. Send the client your verification tag and explain what it's for.
2. Ask them to paste it into their site's custom code and publish.
3. Convert, review and hand over the project.
4. Let the client know they can remove the tag afterwards.

If you work across many client sites, the Studio pack on the pricing page is designed for studios moving their clients' sites, with their permission. The full workflow is in the agency workflow for converting client Framer sites.

If someone converts your site without permission

Signed-in users can convert unprotected published sites. A download costs 1 credit with ownership verification or 10 credits with an explicit ownership-or-permission confirmation. To block both routes inside Deframer, use site protection: verify control, then activate for 10 credits once. It also blocks new conversions and previews while active. Third-party tools may ignore its optional browser helper.

If you believe a site was misused, report misuse.