Both formats are good at different jobs. Here's what a PDF still does better, what a web page does better, a quick way to pick (or send both), and the prompt we used to have AI lay out the page, with what it got wrong when we ran it.
This one is for brand designers who take on client work and already use AI somewhere in how they work.
Two years after you delivered the identity, the client's new marketing hire messages you: which green is the primary? They have the guidelines. It's the PDF from launch week, version one, from before you changed the secondary palette. The printer has the same PDF. So does the freelancer who took over their Instagram last spring.
Nobody did anything wrong. A PDF is a copy, and everyone who got one is holding the version from the day they got it. That's sometimes exactly what you want, and sometimes the problem. Which one it is depends less on the format than on who's opening it.
The usual version of this question is about presentation: a PDF looks like a designed document, a web page looks like a website. That matters on handover day, when the client flicks through it once. It matters much less afterwards.
The more useful question is who opens the guidelines after you've gone, and what they need when they do. Usually that's the printer, the agency building the website, the freelancer doing social, the next designer, and whoever the client hires into marketing. Most of them come to look up one thing, a HEX value, the clear space, whether the mark can sit on the brown, and then close it again. Some of them need the opposite: one file that doesn't move, so they can print from it or point to it later.
Both of those are real needs. The two formats are good at different ones.
What a page doesn't replace is the files people produce work from. The printer still needs your master files, and probably a print-ready PDF. The page tells people the rules and points them to the files.
| Situation | Send |
|---|---|
| A printer is about to run packaging or signage | A print-ready PDF, with the master files |
| The guidelines go into the contract or final invoice as what was delivered | A PDF of that version |
| People mostly look up a colour or a rule, often on a phone | A web page |
| The brand is still moving: palette tweaks, new sub-brands, new templates | A web page, with a version line at the top |
| Someone needs it with no connection | A downloaded PDF |
| A few years of all of the above | Both: the page as the live copy, a PDF of each signed-off version |
Sending both is less work than it sounds. The page is the one you keep current. Each time the client signs off a change, you save a PDF of that version for the record, and the page's version line says which one is current.
If the identity is finished, an AI assistant can lay the guidelines out as a single page in a few minutes. You don't need to build a website. Your time goes into checking what it made, which is what most of this section is about.
The AI is laying out decisions you've already made. Have these to hand before you open the chat:
If you don't have something yet, leave it out of the prompt rather than asking the AI to fill it in. It will fill it in, and it will look plausible.
This is the prompt we ran in Claude, with a made-up client. We asked for plausible example values because we were testing the layout. For a real handover, replace the last paragraph with your client's name and your actual values and rules.
I'm a freelance brand designer. I've finished an identity for a client and I want to hand over the brand guidelines as ONE self-contained HTML page instead of a PDF, so the client's future designers, printers and social freelancers can open it in a browser. All CSS inline, no external fonts, images or scripts.
Include: brand story in a few lines; logo usage rules (clear space, minimum size, don'ts) with the logo drawn as inline SVG; colour palette as swatches with HEX, RGB and CMYK and a one-click copy for the HEX; typography (name the typefaces, show the hierarchy using system fonts as stand-ins and say so); tone of voice do/don't; a "Downloads" section with placeholder links to where the source files live; a version number and "last updated" at the top.
Placeholder client: "Fernhill Coffee Roasters". Make the colours and rules plausible examples.
What came back was a single 24 KB HTML file with no external fonts, images or scripts. Everything we asked for was there: the story, logo usage with clear space, minimum sizes and six don'ts, five swatches with HEX, RGB, CMYK and a copy button, a type specimen and hierarchy, a do and don't list for tone of voice, a Downloads table with placeholder links, and the version and date at the top.
It also had problems. Here's what to check, in the order we'd check it.
Look at the logo before anything else. In our run the wordmark was cut off at the right edge: FERNHILL came out as FERNHILI, on every lockup on the page. It's easy to miss, because it still reads as a word.
The file shows why. The AI drew the logo itself, as an SVG with the name set as live text in Georgia, inside a drawing area that wasn't wide enough for it, so the last letter was cut off. Live text also depends on the fonts installed on whatever device opens the page, so the same logo can come out differently on someone else's screen.
For a real brand, don't let the AI draw the logo. Export your master as SVG with the type outlined, and paste that SVG code into the page in place of the AI's. Then the logo on the page is the logo, not a sketch of it. Do the same for the don'ts: ask the AI to reuse your SVG for the stretched, recoloured and rotated examples instead of redrawing it.
Four things:
The section links and print styles are layout, so keep them if you like them. The other two are brand decisions. The proportion bar is a rule about how much of each colour to use, and the printer note is production advice, and nobody made either decision. A guidelines page is where people go to find out what's been decided, so anything on it gets followed. If you didn't decide it, delete it. Or decide it, and then keep it.
All of them, but look hardest at the CMYK. In our run the CMYK values were a straight formula conversion of the HEX. Fern Green, #2F4A3A, became C37 M0 Y22 K71, which is the same number the textbook RGB-to-CMYK arithmetic gives, give or take rounding. It isn't a value from a print profile, a swatch book or a proof. A printer who takes it as the target will match the formula, not your green. Put in the CMYK (and the Pantone, if you use one) that you actually specified.
The same goes for the minimum sizes (it wrote 35 mm and 140 px for the lockup), the clear-space rule, and the brand story, which it wrote from nothing. They were plausible because we asked for plausible. In a real handover, every one of them should come from you.
We asked for no external fonts, and the AI did what we asked: it named the typefaces (Fraunces and Inter, in our example), showed the hierarchy in Georgia and the device's default sans-serif, and put a note on the page saying so. For a lot of guidelines that's enough. The page has to tell people which fonts to use. It doesn't have to be set in them.
If you want the page set in the real fonts:
@font-face rules that point at them.In our test, yes. In Chromium, with clipboard access allowed, clicking Copy HEX on Fern Green put #2F4A3A on the clipboard and the button changed to "Copied #2F4A3A". Browsers and hosts can restrict clipboard access, and we haven't tried the button on every host, so click it once on the final link before you send it. If it doesn't copy there, the HEX is still printed on the swatch.
Not on the page. The page carries the rules and an SVG of the logo for reference. People produce work from the master files: .ai and .eps logos, print PDFs, swatch files, packaging dielines. Keep those in a shared folder in Google Drive or Dropbox, and use the page's Downloads table to point to them.
Our run produced that table already, with placeholder links for the logo pack, colour swatches, fonts, packaging templates and social templates. Replace each placeholder with the real folder link, and delete the rows for anything you don't deliver.
[Designer name] and [designer email] for you to fill in.Whether the client keeps one address for years depends on where you host the page. You need somewhere that lets you replace the file without changing the link. On miinideck:
If you're sending both formats and want the PDF to stay at one address too, how to update a PDF you've already sent without changing the link compares what Google Drive, Dropbox and others say about it.
A few limits to know before you plan around it:
Upload the guidelines page, send one link, and replace the file when the brand changes. Replacing needs a free account.
When the brand is a system rather than a document: several teams using it, an asset library people download from, different access for different people, approvals before anything goes out. Dedicated brand portals such as Frontify and Brandpad are built for that, and a brand that's growing in that direction will outgrow a single page and a PDF alike.
For a small business or a startup whose guidelines fit on one screen-length page, the choice is smaller. A PDF is still the right thing for the printer and the contract. A page is the right thing for the people who'll come back to look something up. Which of those matters more depends on the client, and you're the one who knows who'll be opening it.
A media kit checklist for creators who build theirs with AI: what a brand manager looks for, the prompt line for each section, what the AI did with each one in our test, the red flags to catch before you send it, and how to keep the numbers current in the link you already sent.
A copy-paste prompt that turns ChatGPT, Claude or any chat AI into a client welcome packet your client can read on a phone. What we got back when we ran it, the rules the AI made up on its own, and how to check and update the packet before it reaches a client.
v0 and Lovable build React/Next projects, not single files — so "export" means a folder or a public deploy, neither of which is a quiet private link. Here's how to get a clean build and share the static slice privately.
miinideck turns a single HTML file into an unguessable link with optional password and expiry. Default-private, never indexed.