Selling fonts as downloads: the typeface your buyer has to install before they can judge it
Every other download gets judged as itself: the buyer opens the PDF, plays the preset, reads the pattern. A font gets judged one step later — after it has been installed, found in a font menu, and set in the buyer's own words. Until then it is a zip file and a promise. And the buyer's own words are the worst possible test text for a seller: their brand name with the one accented letter your character set does not have, their headline in the weight that was never in the download, their ampersand. A font seller's whole business is whether a typeface that looked perfect in your specimen survives being typed by a stranger, in their language, in their software.
A font is software, not a picture of letters: state what is actually in the file
Start with the format, because it decides whether the product works at all. Desktop fonts travel as .otf and .ttf files, which are not interchangeable in every workflow, and webfonts travel as .woff and .woff2, which a desktop buyer cannot simply install and use. A variable font is one file containing a whole weight range; a static family is many files, one per weight and style. Those are different products wearing one name, and a buyer holding the wrong one does not have your font in any useful sense.
Say which formats are in the download, how many weights and styles it contains, and name each one the way it will appear in the buyer's font menu after install — the menu name, not just the prettier family name on your listing. A designer hunting a menu of two hundred fonts for the italic they saw in your specimen, filed under a name your listing never used, is a refund being written in slow motion.
Say whether the font is variable or static with the same clarity, and if it is variable, which axes it actually carries. Say what is not included: the webfont files if the licence is desktop-only, the bold if the family ships in three weights, the specimen artwork, the logo in your hero image — which is lettering, not the font, unless it genuinely is. Buyers buy the alphabet in their head; your job is to make the file in the download match it before money moves.
Show the whole character set, not one pretty word
Every font listing shows a beautiful word set large. That is precisely why experienced buyers scroll past it looking for the one panel that matters: the full character set. Show it. Uppercase, lowercase, figures, punctuation — and the characters sellers hide because they are missing. If your font has no proper ampersand, no currency symbols beyond the dollar, or no accented letters for the languages your buyers will type in, that is a fact about the product they deserve to learn from your listing, not from a client deadline.
Show the font doing real work at real sizes. A display face that sings at 120 points and clogs at 14 is a headline font, and selling it as a text font is a promise the outlines cannot keep. Set a paragraph in it. Set a price list, a menu, a mobile screen — whatever your buyers actually make — and show the spacing and rhythm there, including the words with the letter pairs your kerning handled worst, not only the pairs it handled best.
Be honest about OpenType features. If the listing's beauty comes from ligatures, alternates, or swashes, say which applications can actually reach those features, because a buyer in software that cannot open the glyphs panel has bought a plainer font than the one in your pictures. "Includes alternates" is a claim about their software as much as your file.
Licensing is the product: desktop, web, and app are not one purchase
With most downloads the licence is a footnote. With fonts it is half of what is being sold, and most buyer conflict is born here — not from theft, but from a buyer who genuinely could not tell which use they had bought, because the listing sold "the font" as if use were one thing.
Sell the uses as the separate products they are. Desktop use — installing the font to make graphics and documents — is not webfont use, embedding the file on a website, usually counted by pageviews or domains. Neither is app or ebook embedding, putting the font inside a product other people run. If you offer tiers, name each tier by the use, the limit, and what happens past the limit, in the listing, not only in a licence PDF inside the zip that the buyer reads after paying. If one tier covers everything, say that plainly too — simplicity is a feature font buyers will pay for.
Draw the sharing line in the same place. A font file passed to a client's printer, a teammate, or a collaborator is the normal texture of design work; say whether your licence travels with a project file or stops at the buyer, and how many seats a purchase covers. Most font piracy between professionals is an unanswered licence question that someone answered themselves.
State the update expectation alongside it. When you fix a kern pair, add a currency symbol, or expand the language support, do past buyers get the new files, and where do they re-download them? A re-download that works is the cheapest support channel a font seller owns — and for fonts it matters twice, because an old installed version and a new one with the same menu name will fight silently on a buyer's machine, and the bug report will say your font is broken.
Install is the first use: write steps that end at the font menu
The biggest source of font support mail is not taste. It is installation — and it splits by operating system and by application, because a font installed for the system may still be invisible to the one program the buyer opened first, until it is restarted or its cache clears.
Write the install paths separately, each starting from the file the buyer actually downloaded: unzip, install, then the checkable result — after this step you should see this family name, in this menu, in this application. Name the failure points you already know. The application that must be closed and reopened before the font appears. The duplicate-version warning that means an older copy is already installed and must be removed first, or documents will render in the wrong cut. The webfont kit that a desktop buyer is trying to install because the zip put every format in one folder with no map.
Name the files inside the zip like a map, too: one folder per use, each with its licence, so the file a buyer needs is findable six months later without re-reading your listing. And test your own instructions on a machine where the font has never been installed. Install steps written from memory, on the computer the font was designed on, skip exactly the steps a first-time buyer will trip on.
A short launch checklist for font sellers
- Name the formats in the listing — .otf, .ttf, .woff/.woff2 — and say which uses each is for.
- Count and name every weight and style as it will appear in the buyer's font menu.
- State whether the font is variable or static, and which axes a variable font carries.
- Show the full character set, including punctuation, figures, and currency symbols — and say plainly which characters and languages are not covered.
- Set real text at real sizes, including a paragraph, not only a display word.
- Sell each licence tier by use and limit — desktop seats, web domains or pageviews, app embedding — in the listing, not only inside the zip.
- Write separate install steps per operating system, each ending at a checkable result in the font menu, and state where past buyers re-download updates.
A note on delivery, because every step above ends at a download: I build FileFreight for sellers of files like these — flat-rate digital delivery with licence keys, where you connect your own Stripe account, Pro is $19/month with 0% platform fees (a free tier takes 5%), sales tax and VAT handling stay with you as the seller, there is no font or typeface importer, and it is not a Shopify app. Whatever you deliver with, judge it by the test in this article: the buyer installs on a machine and in software you will never see, so the delivery — file, format, licence, install page, and re-download — has to work without you in the room.
Top comments (0)