The Made with Anticode badge: which plans show it, and what else names Anticode

What the badge looks like

It's a small dark pill, fixed to the bottom-right corner of the window, reading "Made with Anticode" and linking to anticode.dev in a new tab. It's plain HTML and CSS, like the rest of a published page, so it adds no scripts. It has a visible focus outline for keyboard users and is hidden when the page is printed, so a printed menu or price list doesn't carry it. Because it's fixed to the corner and sits above the page, it can cover a little of whatever is beneath it on a narrow phone screen as visitors scroll.

Which plans show it

The "other credits" are small: a generator tag in the code of published app pages, and the line at the top of the generated Privacy Policy and Terms saying Anticode wrote them. On Agency sites the tag is taken out and that line no longer names Anticode. The white-label plan page covers the rest of what Agency changes.

Why upgrading needs no republish

Your published HTML never contains the badge. When a visitor requests a page, Anticode checks the owner's plan and, for a free account, adds the badge just before the closing body tag. The plan is remembered for a few minutes so busy sites don't look it up on every view, which is why a change of plan shows within about five minutes rather than instantly. The same is true in reverse: if a paid plan lapses, the badge returns without anything being republished.

It also means editing your page can't remove it. The badge isn't in the code you see in the Code tab, so there's nothing there to delete. The only way to remove made with badge website builder branding from an Anticode site is to publish it from a paid plan; see pricing for what each costs.

What still mentions Anticode on a paid site

Being honest about this saves surprises when you hand a site to a client. On Pro, Max and Team:

• The address. A site on <name>.anticode.dev has Anticode in its address. Paid plans can publish to your own domain instead.
• The legal pages' credit line, which says the documents were generated by Anticode.
• The hosting disclosure in the Privacy Policy, which names Anticode as the host and Cloudflare as the network. This stays on every plan, Agency included, because it tells visitors who handles their data.
• The security report at /.well-known/anticode-security, which is by Anticode by nature.
• The optional footer link "Security-checked by Anticode", only if you switch it on in the Console's Security section.

Free plan, in context

The badge is one of a few differences on the free plan. Free sites publish only to an anticode.dev address, and their forms keep a monthly allowance of submissions visible; beyond it, submissions are kept but held until you upgrade. Everything else about publishing is the same: the same design and security checks, the same per-site files, and the same cookieless analytics.

Limits

• No per-site choice. The badge follows the owner's plan for every site they own. You can't keep it on one site and remove it from another.
• No custom badge. You can't restyle it, move it or swap the text on the free plan.
• Team workspaces follow the owner. A site published from a Team workspace belongs to the workspace owner and follows the owner's plan.

Questions people ask

How do I remove the Made with Anticode badge?

Upgrade to any paid plan. The badge stops being added to your pages within a few minutes, with no need to publish again.

Does the badge slow my site down?

It's a short piece of HTML and CSS with no script and no image, added to the end of the page.

Will the badge show on a printed page?

No. It's hidden when the page is printed.

Can I hide the badge with my own CSS?

No. It isn't part of your published code, and the code editor doesn't keep arbitrary CSS changes.