A link page has two states: draft and published. Only a published page is reachable by anyone but you.

A published page can also have a draft of its own — a working copy of the page that nobody outside your workspace can see. When that's the case the live page and the draft are two different documents, and the rest of this page is mostly about the gap between them.

Your handle

The handle is the page's public address: itsjustbig.com/t/<your-handle>.

• Claimed at creation. You pick it when you create the page, before you've built anything, so the address is yours while you work.
• Globally unique. Handles are unique across all of big, not just your workspace — if it's taken, you're told before you submit.
• 3–30 characters, lowercase letters, digits, and ., -, _. It must start and end with a letter or digit, and can't contain two separators in a row (my..page and my-.page are rejected). Uppercase input is lowercased for you rather than refused.
• Reserved words can't be claimed. Roughly ninety terms are held back: big's own routes (docs, login, settings, forms, inbox, …), brand and product words (big, links, bio), and trust terms people use for impersonation (official, verify, support, billing, security, instagram, …). You'll get a "that handle is reserved" message, distinct from "that handle is taken".

Publishing

Publish from the editor. Until you do, the page's content never leaves big — a draft isn't just hidden behind a check, it's excluded from the public lookup entirely.

An unknown handle, a draft page, a reserved word, and a temporary lookup failure all return the same 404. A visitor can't use the public page to work out whether a handle exists as a draft.

Unpublished changes

Once a page has a draft, the editor shows an Unpublished changes panel above the action bar. It tells you when the draft was last saved and summarises what would change if it went live:

2 blocks added · 1 block edited · Blocks reordered · Theme changed · Bio is now "Everything I make, in one place."

It's a summary, not a preview — counts and field names, never the block contents. That's deliberate: if a draft was written by an agent, the one place you shouldn't be reading whatever it typed is the screen where you decide to make it public.

Two things follow from a draft existing:

• Visitors still see the published version. Nothing in the draft is on your /t/ URL, and nothing gets there by waiting.
• Nothing in it goes live until a publish covers that exact draft. A publish names the draft it read, so a change made after you looked at it isn't carried along quietly.

If the page has never been published, the same panel says so instead: nobody can see it yet, and these are the changes that will go live the first time you publish.

Version history

Every publish leaves a version behind — a frozen copy of exactly what went live, in the editor's version history, newest first. Each row says when it went live and where it came from: from the dashboard, from an API token, or from an agent.

Restore copies a version back into your draft. It never changes the live page on its own — that's the point of it. A restored version sits in the draft like any other unpublished work, you can edit it further, and it goes live only when a publish does. Restoring overwrites whatever is in the draft, including edits an agent may have made minutes ago, so the confirmation says so before it happens.

History keeps the last 10 versions of a page. From the 7th, the editor starts telling you how many publishes are left before the oldest one rolls off. When the 11th version is published, the oldest is deleted to make room.

That roll-off never blocks anything. Publishing is the one action that always has to work — a page that couldn't go live because its history was full would be a storage limit causing an outage — so the old version goes rather than the publish. The warning from 7 is what gives you three publishes of notice while the version you might want is still there. If there's an old version you want to keep, restore it into the draft before it rolls off.

Approving a publish an agent or the CLI asked for

Publishing is no longer dashboard-only. The CLI, the API and an AI agent connected to your workspace can all ask to publish a page — but none of them can finish the job. A person has to approve it in the browser, every time.

How it goes:

1. The tool asks to publish and gets a short code back — something like BRZK-4QT2 — printed in the terminal or handed to you by the agent.
2. You open the page in big and go to Review and approve a publish (the link is in the Unpublished changes panel, at /links/<page>/approve).
3. The screen shows you the same summary of what would go live, read from the page itself rather than from anything the tool told us.
4. You enter the code. The publish goes through, and not before.

A few things worth knowing:

• The code expires after 10 minutes and works once. If it's gone stale, ask for the publish again and you'll get a fresh one.
• Only an owner or admin can approve. Editors can build and edit the page, but the person consenting to put it on a public URL is an admin.
• The approval is bound to the draft it was asked for. If the draft changes after you approve — an agent edits it again in the gap — the approval no longer matches and the publish is refused rather than shipping something you never read.
• Approve only a code you can see yourself, on a terminal you're looking at or from an agent you just asked. A code someone sends you is not a reason to approve anything.
• Unpublishing needs no code. Taking a page down is the thing you do when something went wrong, so it's never harder than putting it up.

Publishing from the dashboard needs no code either — you're already the person the code exists to find.

What big. adds to your page

Two things appear on every published link page, below whatever you built:

• The "made with big" badge, pinned to the bottom of the screen while the visitor scrolls. It's on every page on every plan, and there's no way to remove it.
• A footer row — About · Report · Terms · Privacy. About explains what big is to a visitor who's never heard of us, Report lets anyone flag a page that breaks the terms, and the last two open big's legal pages in a new tab.

Neither is themed: they stay a dark panel whatever background and colours you pick, so they read as big's rather than yours. Nothing in either one collects a visitor's details or interrupts your page — the footer row is quiet type below your last block, and About and Report only open when tapped.

Anyone can report your page, including people who don't have a big account. Reports go to us, not to you, and we don't tell the reporter who you are. If a page breaks the terms we may remove content or suspend the account behind it — see Report a page for what we act on.

Unpublishing

Unpublishing returns the page to draft. The URL immediately 404s again, and the handle stays yours.

The short links your link blocks minted are not deleted when you unpublish — they keep redirecting, and their click history is intact.

Your version history isn't touched either: unpublishing changes where the page is reachable, not what it says.

Renaming a handle

You can change the handle later. The new one goes through the same format and reserved-word checks.

Be deliberate about it: the old address stops working the moment the rename lands, there's no redirect from it, and it becomes claimable by someone else. Anything already printed or posted with the old handle breaks.

Renaming stays a dashboard action — no token, CLI command, or agent can do it. A rename releases the old handle the same second, and a script watching for one could claim it before you'd finished typing.

Deleting a link page

Deleting the page does not delete the short links it minted. Their codes keep redirecting and their click history survives — they're simply flagged as no longer belonging to a page. Since nothing owns them any more, they don't appear in Links → Short links by default: click Show them too above the list to find them, and delete them there if you want the redirects gone as well. See Links created for you.

Deleting is dashboard-only too, for the same kind of reason: it takes the page's whole view history with it, and there's no undo.