Every identity project ends with the same question from the client: "Can you send the guidelines?" What they mean by "send" tells you almost everything about which format will get used. A founder wants a link they can forward from a phone. A marketing manager wants a file for the shared drive. Procurement wants a deliverable with a version number on it. The PDF and the online page are not competing ideas, they are answers to different requests, and the wrong choice is the one nobody opens six months later.
What a PDF does well
A PDF is portable. It goes in an email, a Dropbox folder, a Notion page and a printed binder without asking anyone to sign in. It prints, which still matters for packaging, signage and any supplier who works from paper. It works offline, on a train, in a factory with no guest Wi-Fi. It is a deliverable in the plain sense: a file with a date, a version, and a line on an invoice. It archives cleanly, because a PDF made today will open in fifteen years. And it is yours. No hosting fee, no service that might close, no account to renew.
For designers there is one more advantage. A PDF is a fixed layout, so the page you designed is the page the client sees. Typography, spacing and the sequence of the argument survive intact.
Where a PDF fails
Versions drift. You send v3, the client forwards v2 to a printer, and the new colour code never reaches them. Files get lost in drives, renamed "brand guidelines FINAL final", and reattached from a two-year-old thread. Colour codes cannot be copied cleanly: select a HEX in a PDF and you get the value with a stray line break, or the label along with it, or nothing because the text was outlined. Nothing can be downloaded from inside it. The logo on page 12 is a picture of the logo, not the file, so the client screenshots it and sends a JPEG to the web agency. And a PDF cannot tell you whether anyone has opened it.
What an online page does well
One address. The client bookmarks it, and every person they forward it to sees the same version. Always current: fix a Pantone reference and everyone has it, with no re-send. Copyable codes: HEX, RGB and CMYK as text that survives a paste into Figma, Canva or an email signature. Downloadable files, next to the rule that governs them, so the correct SVG is one click from the sentence that says where to use it. Viewable on a phone, which is where founders read things now. Some hosted tools also show who visited, which helps when you are chasing a rollout.
Where an online page fails
It needs hosting, which usually means a subscription, either paid by you or handed to the client. It can disappear: if the service shuts down or the card expires, the brand's rulebook goes with it. Some clients want a file, full stop, and their legal or IT department will ask for one regardless. Print suppliers still work better from paper. And a page reflows, so the pacing you designed in a fixed document becomes a scroll that anyone can skim past.
The hosted tools, briefly
Several products host guidelines as web pages. Corebook° positions itself as a brand guidelines platform for branding teams and agencies, with asset management built in. Brandpad is a template-led guidelines builder aimed at designers delivering to clients. Frontify is the enterprise option, pairing guidelines with a full digital asset management system for large organisations. Bravemark is built for freelancers and small studios who want a guidelines page with downloadable assets in minutes. Standards targets design-led organisations and agencies with individual and enterprise plans. All five have their own pricing pages, and the plans change often enough that you should read them directly rather than trust a summary.
The hybrid that works
The most durable setup is not a choice between the two. It is a hosted page as the source of truth and a PDF summary as the deliverable. The page holds the living material: codes, files, do's and don'ts, the latest logo versions. The PDF holds the argument: strategy, the story behind the mark, the pages that need fixed layout, and a link on the last page that points to the hosted address.
Two rules keep the hybrid honest. First, the PDF says on its cover which version it is and where the current one lives. Second, whenever you change a colour or a file, you update the page the same day and the PDF only at the next milestone. Clients understand "the page is always right, the PDF is a snapshot" as soon as you say it.
If you make the guidelines PDF in Illustrator, generating it from the same swatches and logo artwork you publish online removes the main cause of drift, because both outputs come from one file. That is the workflow Anchr Guide and Anchr Portal are built around, and any careful manual process gets you the same result.
What to tell the client
Say it in the kickoff, not at handover. Tell them they will receive one hosted address and one PDF, explain which is which, and name the person on their side who owns the link. Explain that copying codes from the page is safer than retyping them from the PDF. Explain that the hosted page is what they should send to a web developer or a printer, and the PDF is what they should keep in the drive. If the page has a subscription, say who pays for it and what happens if it lapses. Put all of this in the proposal as two lines, and you will never have the "which file is right" conversation.
Decision table by client type
| Client | Primary format | Secondary | Why |
|---|---|---|---|
| Solo founder | Hosted page | Short PDF, 1 to 20 pages | Reads on a phone, forwards a link, needs codes and files more than theory |
| Small company with a marketing person | Hosted page | Full PDF, 40 pages | The marketer wants copyable codes daily and a file for the shared drive |
| Agency working for you | Hosted page for files | Agencies read fixed layouts closely and archive by version | |
| Enterprise | Their own platform or a PDF | Hosted page as a handover | Enterprise teams already run Frontify or similar; your job is to hand over cleanly |
The pattern: the smaller the client, the more the hosted page matters, because nobody on their side will maintain a file system. The larger the client, the more the PDF matters, because they have systems, versions and people whose job is to file things.
Questions
Should I charge separately for a PDF and an online page?
Charge for the guidelines once, as a deliverable, and treat the hosted page as the distribution method. If the page carries a monthly cost, list it as a line item with a named owner so the client knows what lapses if they stop paying. Bundling both into one fee is simpler and avoids the client choosing the cheaper format for the wrong reason.
What happens to the online guidelines if the service closes?
You lose the page unless you kept an export. This is the real argument for the hybrid: keep the PDF, keep the source Illustrator file and the exported logo files locally, and treat the page as a mirror. Choose a service that lets you download the assets and rebuild elsewhere, and check that condition before you commit a client to it.
How many pages should the PDF have?
As many as the client will read. A founder reads twenty pages, a marketing team uses forty, and one hundred pages suits a brand with sub-brands, packaging systems and motion rules. The last page of any length should carry the hosted address. Anything longer than the client's attention is padding, and padding is where errors hide.
Can a client copy colour codes from a PDF reliably?
Rarely. Text in a PDF can be outlined, split across lines, or laid out in a table that pastes as one string. If the PDF is the only format, set the codes in live text, one value per line, in a monospaced face, and test the copy yourself. Better, point the client to a page where each code is a button.
Do it in one click
Anchr Guide fills one of 22 brand guidelines templates (1, 20, 40 or 100 pages) from the open Illustrator file: brand name from the document name, up to six colours from named swatches in HEX, RGB and CMYK, the fonts in use, and the three logos from the selection. The output is a PDF that also opens in Illustrator, and Apply Changes updates an open guidelines document when a colour or font changes. Anchr Portal publishes the same brand as a hosted page at anchr.tools/b/your-brand, with click-to-copy codes, typography specimens, logo files for light and dark backgrounds, do's and don'ts and a "Download all" zip. The client needs no account, each publish is a new version at the same link, and client portals are not indexed. See an example portal.