Link pages
Link pages and short links sit side by side under Links in the sidebar: a link page is one hosted page at
itsjustbig.com/t/<handle>holding many buttons, a short link is one redirect at/l/<code>. Every link button you add to a link page mints a short link behind the scenes.
A link page is a list of blocks stacked on one public page. You build it in the dashboard, pick a theme, publish it, and share one URL.
What a link page is made of
| Part | What it is |
|---|---|
| Handle | The public address: itsjustbig.com/t/<handle>. Unique across all of big |
| Profile | Avatar, display name, and a short bio, shown above the blocks. |
| Blocks | The stacked content: link buttons, form buttons, a socials row, images, and section headers. See Blocks. |
| Theme | Background, accent colour, button shape and fill, font, avatar shape. See Theme. |
| Status | draft or published. Only a published page is reachable. See Publish and handles. |
Create one
- Open Links in the sidebar and choose New link page (editor role or higher).
- Enter a handle — this claims the address immediately. Typing a display name suggests a handle for you.
- Optionally enter a display name. Both can be changed later.
You land in the editor with three tabs:
- Build — profile fields and the block list.
- Theme — colours, fonts, button styling, background.
- Stats — page views and per-block numbers (see Link page stats).
Build and Theme share one unsaved-changes state, so switching between them keeps your edits; Stats is a real navigation and will prompt you if you have unsaved work.
Profile fields
- Display name — up to 100 characters.
- Bio — up to 300 characters.
- Avatar — picked from your Files; it must be an uploaded image that finished processing.
Link pages and forms point at each other
Both directions exist, and together they close a loop:
- A link page → a form. Add a form block and the page renders a button to one of your workspace's forms. See Blocks.
- A form → a link page. A form's post-submit screen can offer a button to one of your link pages, so someone who has just submitted lands on everything else you're sharing rather than on a dead "Thanks!". See The confirmation screen.
The second direction is what lets one link in your Instagram bio do two jobs: it points at the form, so the visit becomes a lead, and the thank-you hands that person your page.
Limits
There is no plan cap on link pages, blocks, or views — every plan gets the same. Two technical bounds exist purely to keep a page sane: a maximum of 200 blocks, and the whole block definition must serialize to under 64 KiB. Neither is reachable by building a page by hand. A workspace also keeps at most 100 link pages, flat on every plan, which in practice only shows up when pages are being created from a script.
Building a page outside the dashboard
Link pages have a programmatic surface: the API (scopes link-pages:read and link-pages:write), the CLI (big link-pages, big link-page:view / :create / :edit / :publish / :revisions / :restore), and both MCP servers for listing, reading, creating, and asking to publish.
It goes as far as asking, and a person finishes it. You can list your pages, read one in full, create one, edit one while it is a draft, read its version history, and restore an old version into the draft. Publishing and unpublishing are reachable too — but a publish asked for by a token, a command or an agent doesn't happen until someone approves it in the browser, at the page's own approve screen. See Approving a publish.
Two things stay dashboard-only, on purpose rather than pending:
| Dashboard-only | Why |
|---|---|
| Renaming the handle | A rename releases the old handle immediately, with no redirect — see Renaming a handle. A script watching for renames could claim it the same second. |
| Deleting a page | It takes the page's whole view history with it, and there's no undo. |
Editing a page that's already published is still refused as well. Your audience already has that URL, and a one-shot overwrite of a live page isn't the same act as editing a draft — unpublish it, or edit the draft and publish that.
Three more things worth knowing before you point a script at a page. A write has to carry the updatedAt you read, so an edit that raced a person editing in the dashboard fails instead of quietly overwriting them. A saved block can't be repointed at a new URL once it has minted its short link — that /l/ code may already be in a bio or a printed QR code — so remove the block and add it back, which mints a fresh one. And creating a page over a token is refused once the workspace holds 100 of them, with a warning from 70 that names the pages nothing has visited lately. All three are explained in Link pages.
Editing exists on the CLI and the API but not on either MCP server: a page's blocks are replaced wholesale, and that is a bigger thing to hand a model reading DMs than a person typing a command. See Editing a link page is CLI-only.
What's not there yet
- No custom domains. Every page lives under
itsjustbig.com/t/. - No per-block scheduling or expiry. A block is either visible or hidden.
Where to go next
- Blocks — the five block types and what each needs.
- Theme — every styling option.
- Publish and handles — going live, renaming, reserved words.
- Link page stats — views, clicks per block, form views.