Core concepts

PageFork’s core concepts are sites (projects), pages (URLs), versions (snapshots of every edit), credits (the unit of AI work), model tiers (Standard / Advanced / Premium), and site plans (Basic or Pro, per site, monthly or yearly). This page defines each one.

You don’t have to memorise it — but if you read it once, every other doc will make more sense.

Site

A site is one project. It has its own editor, its own chat history, its own pages, and its own publish settings. You can have many sites under a single account. New sites show up in the sidebar under Recent Sites, and the full list lives under All Sites.

Page

A page is one URL within a site, e.g. /, /pricing, /about. A site can have one page or many. PageFork decides which pages to create based on your prompts — you can always add more by asking (“add a pricing page”).

Version

Every edit produces a new version of the site. Versions are what power undo/redo — you can roll back at any point without losing your chat history. The version shown in the preview is the current one; publishing freezes one specific version and serves it from the public URL.

Block

A block is any visible element on your page — a headline, a card, a button, a pricing row, a footer link. Blocks are what you point at when you want to change “this specific thing” instead of the whole section. See Selecting blocks for how to reference them in chat.

Chat message

Every message goes through the same composer. PageFork decides per message whether to:

• Answer — reply in chat without changing the site.
• Edit — generate a new version of the site.

Both consume credits, but answers are usually cheaper because PageFork doesn’t rewrite your site. See Questions and edits.

Credit

A credit is the unit of AI usage. Each generation, edit, question, or retry consumes credits based on how much the AI has to think and write. You buy credits in packs, they never expire, and one balance is shared by every site in your team. New accounts start with 25 free credits. See Credits explained.

Auto top-up

Auto top-up is an optional setting under Billing → Credits. You pick a pack and a threshold; when your balance drops below it, PageFork buys that pack with your saved card — at most twice per calendar month. See Auto top-up.

Model tier

A model tier is the quality level for an AI run: Standard, Advanced, or Premium. You pick it in the composer before generating or editing. Higher tiers usually produce stronger results and cost more credits. See Model tiers.

Site plan

A site plan is what puts a site on the internet. Each site has its own plan, billed monthly or yearly, and one team can mix plans across its sites:

• Basic (€5/month or €50/year) — hosting on your own domain with SSL, publishing, forms, the submissions list with CSV export, and notification emails.
• Pro (€14/month or €140/year) — everything in Basic, plus leads, people, destinations, Zapier and Make, and the analytics dashboard.

Without a plan for a site, you can still edit it and share it by preview link — you just can’t publish it to a live URL. Unpublished drafts cost nothing to keep. See Basic and Pro plans.

Pro trial

Every new site starts with a 14-day Pro trial: the full Pro feature set from day one. When it ends, a site without a Pro plan has Basic features. Nothing is deleted — forms keep capturing, and leads and analytics keep building in the background, ready the moment the site is upgraded.

”Built with PageFork” footer

Published Basic sites show a small Built with PageFork credit at the bottom of every page. Pro removes it.

Storage allowance

Files you upload to the media library count towards your team’s storage allowance: 100 MB or 100 files free, plus 500 MB / 500 files for each Basic site and 2 GB / 2000 files for each Pro site. When it’s full, new uploads are refused until you delete files or add or upgrade a plan — nothing is ever deleted for you. See Storage allowance.

Preview link

A preview link is a private URL that shows your current draft to anyone you send it to — no account, no domain, no plan. It’s how you share work before going live, and it’s free. See Preview links.

Custom domain

A custom domain is a domain you own (like acme.com) that you point at your PageFork site. It requires a plan for the site and a quick DNS setup. SSL is automatic. See Connecting your domain.

A custom domain isn’t optional: a site goes live on your own domain or not at all. PageFork doesn’t host finished sites on a shared pagefork.ai address.

The lifecycle, visually

prompt/template
     │
     ▼
  version 1  ──edit──▶  version 2  ──edit──▶  version 3  …
                            │                      │
                 preview    │                      ▼ publish
                 link ◀─────┘                 live at
                 (free, any version)          acme.com
                                              (your own domain)

Every edit creates a new version. Publishing snapshots one version and serves it. Editing after publishing creates new versions without affecting the live site — until you publish again.