# Custom Font Builder Instructions

**By Marshall Atkinson, Atkinson Consulting (marshallatkinson.com)**

Use this file to turn an image of your alphabet into a real font you can install and type with in Adobe apps, Affinity, CorelDRAW, Office, Canva and embroidery software.

You don't need font software. You don't need to write code. The AI does the technical work.

---

## How to Use This File

1. Check your alphabet image against the list in **Part 1**.
2. Open a new chat in Claude or ChatGPT. Upload **this file** and **your image or images** together. You can upload more than 1 sheet (for example, 1 for capitals, 1 for lowercase and 1 for numbers and punctuation).
3. Type: **"Follow these instructions and build a font from my sheet."** The AI uses your image's file name as the font name, so name the image what you want the font called (for example, `Capone.png`). If you want a different name, add "Call it [Your Font Name]."
4. Review the preview the AI sends back. Ask for fixes in plain English (see **Part 5**).
5. Download your font files and install them (see **Part 6**).

**What you need:** an AI chat that can run code and create files. Claude has this built in. In ChatGPT, use a model with code tools turned on. This process has been tested in both Claude and ChatGPT. Claude gave the smoothest curves in testing. If your AI says it can't run code or can't create files, switch tools.

---

## Part 1: Check Your Art Before You Upload

- [ ] Plain white background, solid black characters
- [ ] Large, sharp image (2048 pixels wide or larger is ideal)
- [ ] Full character set if you want it: caps, lowercase, numbers 0 to 9, punctuation and symbols
- [ ] Characters don't touch or overlap their neighbors, as much as possible
- [ ] Rows have a clear gap between them
- [ ] The image file is named what you want the font called (for example, `Capone.png`)
- [ ] If this is another weight of a font you already built (for example, a Thin version), you know the family name to match
- [ ] You own the rights to the art (see **Part 8**)

**One sheet or several?** A full font needs about 100 characters. Image tools often give you capitals only. If that happens, make 2 more images in the same style (one for lowercase, one for numbers and punctuation) and upload all of them together. In Midjourney, use your first image as a style reference so the hand stays consistent.

**What happens if characters are missing?** The AI can build a few missing marks, like dashes or quotes, from your art. If whole groups are missing, such as all the numbers, it will stop and ask whether you want to upload another sheet or build a capitals-only display font.

Don't worry if it isn't perfect. The AI can handle touching letters, missing characters and rows drawn at different sizes. It just takes a little more back and forth.

Gray shading and texture can only become solid black or cutouts in a font, because a font is 1 color.

---

## Part 2: Instructions for the AI

*Everything in this part is written for the AI. The reader does not need to follow it.*

You are building an installable font from the attached character sheet. The user is not technical. Do all of the work yourself, show results as images, and explain decisions in plain language. Never ask the user to run commands.

### Hard Rules (Read These First)

These rules come from real failed builds. Break any of them and the font will look wrong the first time someone types a sentence.

1. **Never scale characters one at a time to a fixed height or a fixed box.** Scale whole rows with 1 scale factor per row. Every character in a row keeps its size and vertical position relative to that row's baseline. A period stays small. A g keeps its tail. A + stays the size it was drawn.
2. **Descenders hang below the baseline.** g, j, p, q, y, the tail of Q, commas and any drips must extend below 0 in font units. If a descender letter's top sits lower than the other lowercase letters or its body is smaller, you scaled it individually. Redo it.
3. **Small marks stay proportional.** Periods, colons, semicolons, commas, hyphens, dashes, minus and equals keep their drawn size relative to their row. Never shrink them to specks or blow them up to letter height.
4. **Large marks don't balloon.** +, ×, ^, *, < and > should be no taller than the lowercase x-height to cap height range, and never heavier than the letters.
5. **Scaling must not change stroke weight, and designed contrast stays.** When you scale a row or sheet, its lines get thicker or thinner. Correct that difference so the row matches the capitals. Don't flatten thick-and-thin contrast that was drawn on purpose (brush scripts, calligraphy, serif styles). Compare like with like: the thickest strokes of a row against the thickest strokes of the capitals, and the thinnest against the thinnest.
6. **Compare to the original before delivering.** Put your preview next to the user's sheet and check every row (see 2.11). Fix anything that doesn't match before sending.

### 2.1 Set Up

- Use Python. You need: `fontTools`, `opencv-python`, `numpy`, `Pillow`, `scikit-image`, and a bitmap tracer. Prefer `potracer` (pure Python Potrace port, `pip install potracer`). Install anything missing.
- **Potracer polarity check:** before tracing real glyphs, trace a test image of a filled square with a square hole. Confirm you get exactly 2 contours (outer plus hole). If you get 3, invert the mask you pass in.
- If no tracer can be installed, fall back to `cv2.findContours` (`RETR_CCOMP`, `CHAIN_APPROX_NONE`) on the 4x upscaled, blurred bitmap from 2.4. Smooth the point list with a small moving average (5 to 9 points), simplify with `cv2.approxPolyDP` (epsilon about 1 to 1.5 pixels at 4x), keep sharp corners where the angle changes by more than about 60°, and convert the smooth stretches to cubic curves (Catmull-Rom to Bézier works). Tell the user the curves may be slightly less smooth than a Potrace build. The fallback changes how outlines are traced, never how characters are sized. The Hard Rules still apply.
- Copy the user's upload into a working folder. Don't modify the original.

### 2.2 Review the Sheet First

**Font name.** Use the first of these that applies:

1. A name the user typed in the chat ("Call it ...")
2. The uploaded image's file name, without the extension (`Capone.png` becomes "Capone"). Clean it up: turn underscores and hyphens into spaces and capitalize each word.
3. If the file has an automatic name (for example "ChatGPT Image Nov 19, 2026.png", "image.png", "IMG_1234.jpg", "Screenshot ...", or a string of random letters and numbers), ask the user what to call the font before building.

State the name you're using at the start of your review so the user can correct it.


Before building, tell the user in plain language:

- Which characters are present, row by row
- What's missing (common gaps: hyphen and dashes, opening quotes, ellipsis, underscore, a plain capital I)
- Problems you see: touching letters, rows that touch, letters off the baseline, rows drawn at different sizes, low resolution, gray texture
- How you plan to handle each one

**Completeness gate.** Decide whether you have enough to build a complete font:

| What's on the sheet | What to do |
|---|---|
| Caps, lowercase, numbers and the main punctuation | Build. Fill small gaps from 2.7. |
| Caps and lowercase, no numbers | Stop and ask (below) |
| Caps only, with numbers and punctuation | Build. Map lowercase keys to the capitals and say so. |
| Caps only, no numbers or punctuation | Stop and ask (below) |
| More than about 10 punctuation marks and symbols missing | Stop and ask (below) |

When you stop, explain in plain language what's missing and offer 3 choices:

1. **Upload more sheets** in the same style (recommended). Tell the user exactly which characters to ask for.
2. **Build a caps-only display font now** with the letters available. You'll add only the basic marks that are simple strokes and dots (period, comma, hyphen, dashes, colon, apostrophe, quotes, exclamation point), drawn to match. No numbers or complex symbols.
3. **Build everything anyway,** with the AI drawing all missing numbers and symbols. Warn that invented characters may not look like the same hand drew them.

Don't draw numbers, &, @, $ or other complex symbols from scratch unless the user picks choice 3.

Then build. Don't wait for approval unless something is truly ambiguous (for example, a mark that could be 2 different characters).

If the user says this font is another weight or style of a font they already built, follow 2.9 to group them into 1 family.

### 2.3 Split Rows and Characters

1. Threshold the image (ink = pixels darker than 128 on a 0 to 255 grayscale).
2. **Rows:** use the horizontal ink profile. Gaps with zero ink separate rows. If 2 rows touch (descenders, drips or swashes), find the cut line with the least ink near the expected gap. A minimum-ink path (seam) that can bend around ink works better than a straight line. Check which character each stray piece belongs to.
3. **Characters:** within each row, use the vertical ink profile to find gaps.
   - Merge multi-part characters into 1 glyph: `"` (2 marks), `™` (T and M), `…` (3 dots), `%`, `÷`, and the dot on `i` and `j` if it separates.
   - If letters touch (swashes, script), estimate the count from average letter width and cut with a vertical minimum-ink seam.
4. **Verify the count per row** against the expected characters. If it doesn't match, zoom in on that row and look before guessing.
   - **Confirm lookalikes by shape, not just by order.** In scripts and hand lettering, these are easy to mix up: U, V and Y; I, J and l; O and 0; S and 5; Z and 2; and the 2 halves of a quote pair. Check each one visually before naming it.
   - **Multiple sheets:** split each sheet the same way, then name every character across all sheets. If a character appears on more than 1 sheet, use the cleanest version and say which you used.
5. Render a color-coded check image showing each character's assignment and confirm it visually.

### 2.4 Clean Bitmaps

For each character:

- Crop with about 6 pixels of padding.
- Upscale 4x with cubic interpolation, then apply a light Gaussian blur (sigma about 1.0 to 1.2). Threshold at 128. This smooths jagged edges from low-resolution sheets.
- Remove specks smaller than about 150 pixels (at 4x).
- Fill enclosed holes smaller than about 150 pixels (at 4x). Keep real counters (the holes in O, A, e, 8).
- **Thin hairlines and tapered ends:** brush and calligraphy styles have strokes only a few pixels wide. Count the separate pieces in each character on the original sheet, then count them again after cleanup. If a character broke into more pieces (a crossbar or hairline snapped off), redo it with less blur (sigma 0.6 or none), a slightly higher threshold (140 to 160), and no erosion. A hairline that breaks in the font will print broken.
- **Textured or distressed art:** fonts are 1 color. Test thresholds of 120, 150 and 180, show the user a side-by-side, and pick the one that keeps the character's look without breaking it apart. Highlights become cutouts.

### 2.5 Trace to Outlines

- Trace with Potrace settings: `turdsize` 30 to 60, `alphamax` 1.0, `opticurve` on, `opttolerance` 0.2 to 0.3.
- Convert to font units with y pointing up.
- **Contour direction:** for OTF (CFF), outer contours counterclockwise and holes clockwise. Determine nesting depth with a point-in-polygon test. For TTF, reverse direction (TrueType outers run clockwise) and convert cubic curves to quadratic (`Cu2QuPen`).
- Drop leftover contours with very small area (under about 800 square units) that sit away from the character. These are specks from neighboring characters.

### 2.6 Size and Position

- Units per em: 1000. Cap height: 700.
- **Baseline per row:** the median bottom of characters that sit on the line (exclude descenders like g, j, p, q, y and drips). Descenders, drips and tails hang below the baseline.
- **Multiple sheets:** treat each sheet like a group of rows. Scale each sheet's capitals, lowercase or numbers with the same reference rules below, so a lowercase sheet drawn bigger than the caps sheet still ends up the right size.
- **Rows are often drawn at different sizes.** Pick 1 scale factor per row from a reference character, then apply that same factor to every character in the row (Hard Rule 1):
  - Caps rows: scale so flat-topped capitals (E, H, I, L) = 700
  - Lowercase: scale so ascenders (b, d, h, k, l) = cap height; give the second lowercase row the scale that makes its x-height (n, o, u) match the first row's
  - Numbers: scale so the median number height = cap height
  - Punctuation rows: use `!` or `?` as the reference and scale so it = cap height
  - Symbol rows: use `&`, `@`, `#`, `$` or `%` as the reference (whichever is on that row) and scale so it = cap height
  - Never measure the reference from a descender letter or a small mark
- **Vertical position comes from the sheet.** Place each character so its distance from its row's baseline on the sheet, times the row's scale, becomes its position in font units. That's what keeps dashes at mid-height, quotes at the top and descenders below the line.
- **Even out stroke weight after scaling** (Hard Rule 5). Scaling up a row makes its lines thicker. For each row, measure stroke widths with a distance transform sampled on the skeleton. Compare the 80th to 90th percentile (the main strokes) to the same measure on the capitals, in font units. Erode or dilate that row's bitmaps to close the difference before tracing. Never erode a row that contains hairlines below about 25 font units wide, because they'll disappear. Correct that row by adjusting its threshold instead.
- **Slanted styles (scripts and italics):** measure the slant from the near-vertical stems (H, I, l, n, the downstrokes of script capitals). Use the median angle. Set the font's italic angle in the `post` table (negative for a right lean, for example minus 12) and set the `hhea` caret slope to match, so the text cursor leans with the letters. Keep the style name "Regular" unless the user calls it an italic.
- If letters on a hand-drawn sheet wander off the line, align each to the row baseline. Keep intentional bounce, but fix anything that makes typed words look broken.

### 2.7 Fill In Missing Characters

Build missing characters from parts already on the sheet before drawing anything new:

| Missing | Build it from |
|---|---|
| Hyphen, en dash, em dash | The minus sign or another dash. Lengthen by repeating the middle columns of the bitmap so the end caps keep their shape. Don't stretch. |
| Opening quotes ‘ “ | Rotate the closing quote 180°, or duplicate a single opening quote |
| Ellipsis … | 3 periods |
| Underscore _ | A dash moved below the baseline |
| Plain capital I | If the sheet's I has a dot or odd shape, make a plain stem from a matching straight stroke |
| $ | The S with a vertical stroke through it |
| Lowercase on a caps-only sheet | Map lowercase keys to the capital glyphs |

If nothing on the sheet can be reused, draw the character with a brush that matches the sheet's stroke weight and end shape, render it to a bitmap, and trace it the same way so it matches.

Also map these keys: straight `'` and `"` to the curly closing quotes if no straight versions exist, minus (U+2212) to the hyphen if needed, and non-breaking space to space.

### 2.8 Build Accented Letters

Shops set customer names, and names carry accents: José, Peña, Zoë, Müller, François. Build the Western European set on every font, even if the sheet has no accents.

**Characters to build:** À Á Â Ã Ä Å Ç È É Ê Ë Ì Í Î Ï Ñ Ò Ó Ô Õ Ö Ù Ú Û Ü Ý and à á â ã ä å ç è é ê ë ì í î ï ñ ò ó ô õ ö ù ú û ü ý ÿ, plus ¿ and ¡.

**Make the accent marks from parts already on the sheet** so they match the stroke:

| Accent | Build it from |
|---|---|
| Acute ´ and grave ` | A short, slanted stroke cut from the apostrophe, slash or the sheet's own strokes. Grave is the acute mirrored. |
| Circumflex ˆ | The `^` from the sheet, scaled down |
| Caron ˇ | The circumflex flipped upside down |
| Tilde ˜ | The `~` from the sheet, scaled down |
| Dieresis ¨ | 2 periods, scaled down and placed side by side |
| Ring ˚ | A small O or degree sign, scaled down |
| Cedilla ¸ | A small hook from the comma, placed under the letter |
| ¿ and ¡ | The ? and ! rotated 180°, then moved down so the dot sits near the x-height and the tail drops to the baseline or slightly below |

If the sheet has none of these source shapes, draw the mark with a brush that matches the sheet's stroke (see 2.7).

**Placement rules:**

- Scale accent marks to about 20% to 30% of cap height, with the stroke weight matched to the letters (Hard Rule 5).
- Center each accent over the visual middle of the letter, not its bounding box. For lopsided letters (like a slanted A), center over the letter's widest part.
- On capitals, leave a gap of about 40 to 70 units above cap height. On lowercase, leave the same gap above the x-height.
- For í ì î ï, remove the dot from the i first (it's the topmost separate shape), then add the accent.
- Combine the base letter and accent into 1 outline set (copy the contours) so the result works in both OTF and TTF.
- Accents on capitals sit above cap height. Make sure the font's vertical metrics (2.10) are tall enough that they aren't clipped.

### 2.9 Spacing by Shape, Numbers and Kerning

**Space letters by their shape, not with 1 number for everything.** Equal side space makes round letters look farther apart than straight ones. Professional designers space so the open area between letters looks even.

1. **Set the base space from straight sides.** Use H (caps) and n (lowercase). Start at 40 to 60 units per side. Bold condensed: about 40. Thin or hand-lettered: 50 to 65. Swashy or script: 15 to 25.
2. **Measure each side of every letter.** For slanted styles, first shear each letter upright by the measured slant angle, measure, then use those numbers on the slanted letter. For each side, measure how far the ink sits in from the letter's edge at every height between the baseline and cap height (caps) or x-height (lowercase). Average it. A straight stem measures close to 0. A round side (O, C, o, e) measures more. An open or slanted side (A, V, T, L's right side, r) measures a lot.
3. **Subtract the measured depth from the base space** so the average open area matches H or n:
   - Round sides end up at about 60% to 75% of the base space
   - Open and slanted sides end up near 0, and can go slightly below 0 for letters like T, V, W, Y and A
   - Never let 2 letters touch at text sizes
4. **Test with spacing strings** and look at the render: `HHOHHOHH`, `HOHOHOH`, `nnonnonn`, `nonono`, `HAVHAVH`, `minimum`. The gaps should look the same width. Adjust until they do.
5. Punctuation and symbols: start at about 60% of the base space so `$12.99` and `(Min. 48)` don't look loose.
6. Word space: 200 to 300 units, at least as wide as a lowercase n.

**Numbers: proportional by default, tabular as an option.**

- Space the numbers 0 to 9 by shape like letters. This is the default, and it looks best in headlines and dates like `1993`.
- Also build a **tabular set**, where all 10 numbers share 1 width (the widest number plus base side space on each side), each centered in that width. Name them `zero.tnum` through `nine.tnum`.
- Connect them with an OpenType `tnum` feature (GSUB single substitution, `zero` to `zero.tnum` and so on). Tabular numbers line up in columns on price sheets and order forms.

**Kerning:** after spacing by shape, add kerning for the common problem pairs: AV, VA, AW, WA, AT, TA, AY, YA, LT, LV, LW, LY, FA, PA, Te, To, Ta, Tr, Ty, Vo, Ve, Va, Yo, Ye, Ya, Wo, We, Wa, and T, V, W, Y, F, P before a period or comma. Use small values (minus 20 to minus 60 units). Kerning also needs to cover the accented versions (À with V, and so on), so use kerning classes that group each base letter with its accented forms.

### 2.10 Build the Files

Use `fontTools.fontBuilder` to build both:

- **OTF** (CFF outlines) for design apps
- **TTF** (TrueType outlines) for older programs and embroidery software

Set:

- Family name exactly as the user gave it, style "Regular" (unless it belongs to a family, below)
- A PostScript name with no spaces (for example `MyShopDisplay-Regular`)
- Weight class that matches the look (100 thin, 200 extra light, 300 light, 400 regular, 500 medium, 600 semibold, 700 bold, 800 extra bold, 900 black)
- `fsType` = 0 so the font installs and embeds without restrictions
- Vertical metrics tall enough that accents on capitals, descenders and drips aren't clipped. Set the OS/2 typographic ascender and descender, the Windows ascent and descent, and the hhea ascent and descent so the line height is the same in every app. Set the `USE_TYPO_METRICS` flag (fsSelection bit 7).
- A `.notdef` glyph and a space glyph
- Kerning as a GPOS `kern` feature and tabular numbers as a GSUB `tnum` feature

**Grouping weights into 1 family.** If the user is building more than 1 weight or style of the same design (for example, a Regular and a Thin), they should appear in design apps as 1 family with a style menu, not as separate fonts:

| Setting | Regular | Thin (example) |
|---|---|---|
| Typographic family name (name ID 16) | My Shop Condensed | My Shop Condensed |
| Typographic style name (name ID 17) | Regular | Thin |
| Legacy family name (name ID 1) | My Shop Condensed | My Shop Condensed Thin |
| Legacy style name (name ID 2) | Regular | Regular |
| PostScript name (name ID 6) | MyShopCondensed-Regular | MyShopCondensed-Thin |
| Weight class | 400 | 100 |

- Keep the cap height, x-height, baseline and vertical metrics identical across the family so weights can be mixed on 1 line.
- Bold weights (700) get legacy style name "Bold" under the base family name, with the bold bit set in fsSelection and macStyle, so the B button in Word works.
- If the user built an earlier weight as a separate font, tell them to uninstall the old version before installing the regrouped files.

### 2.11 Test Before Delivering

Render a preview page from the OTF and the TTF at several sizes. Include:

- The full character set, row by row
- A big headline in caps
- A mixed-case sentence with a comma and an apostrophe
- A price line, such as `SAVE 25%! $12.99 EACH (Min. 48 pcs)`
- Every symbol on the sheet
- Names with accents: `José Peña · Zoë Müller · FRANÇOIS ÁLVAREZ · ¿Qué?`
- The spacing strings from 2.9
- A price column of 3 lines (for example `$8.50`, `$12.99`, `$110.00`) set once with default numbers and once with tabular numbers turned on

**Step 1: Run these checks in code** on the finished font (glyph bounds in font units). Each one must pass:

| Check | Pass when |
|---|---|
| Descenders | g, j, p, q, y each have a bottom below 0 (about minus 150 to minus 300) |
| Descender size | the tops of g, p, q, y are within about 10% of the x-height of a, n, o |
| Capitals | every capital's height is within about 10% of 700 (Q and J may extend lower) |
| Small marks | the period is at least 8% of cap height wide; hyphen, minus and equals are at least as wide as a lowercase n |
| Dash order | hyphen is shorter than the en dash, which is shorter than the em dash |
| Large marks | +, ×, ^, *, < and > are no taller than cap height and no wider than a capital H |
| Stroke weight | median stroke width of numbers, punctuation and symbols is within about 15% of the capitals |
| Quotes | opening and closing quotes are the same size, and the doubles are pairs of the singles |
| Baseline marks | the bottoms of the period, comma dot, colon and the dot of ! and ? sit within about 20 units of 0 |
| Word space | the space is 200 to 300 units wide and at least as wide as a lowercase n |
| Accents | all accented letters from 2.8 exist; every accent clears its letter by at least 30 units and sits within about 15% of the letter's visual center |
| Accent clipping | the tallest accented capital fits inside the font's ascender and Windows ascent |
| Spacing by shape | round sides (O, C, o, e) have smaller side space than straight sides (H, n); the spacing strings show even gaps in the render |
| Tabular numbers | all 10 `.tnum` numbers have exactly the same width, and the `tnum` feature is present |
| Family | if part of a family, the typographic family name matches the other weights and cap height matches them exactly |
| Coverage | every character on the sheet, plus anything you built, is in the character map |
| Completeness | the build matches the choice from the completeness gate in 2.2 (complete font, caps-only display font, or everything drawn) and the reply says which |
| Hairlines | every character has the same number of separate pieces as on the sheet (plus any added accents) |
| Contrast | for brush, script and serif styles, the ratio of thickest to thinnest stroke in each row is within about 25% of the capitals' ratio |
| Slant | for slanted styles, the italic angle is set and within about 3° of the measured slant |

If any check fails, fix the cause (usually per-character scaling) and rebuild. Don't just nudge the failing glyph.

**You must run every check in code and report the results.** Don't estimate from the preview, and don't skip checks to save time. Your delivery must include a table like this, with the measured values from the final files:

| Check | Measured | Result |
|---|---|---|
| Descenders | g −210, j −240, p −220, q −215, y −230 | Pass |
| Word space | 250 units | Pass |
| ... | ... | ... |

A build with any "Fail" isn't finished. Fix it and rebuild before delivering. If something truly can't pass (for example, the sheet is missing a character and nothing on it can be reused), mark it "Needs your input" and explain why in 1 sentence.

**Step 2: Compare to the original.** Render the font's character set in the same row order as the sheet and show it directly under or beside the original. For each row, check that the relative sizes, weights and positions match the sheet. Tiny descenders, shrunken punctuation or oversized symbols mean a Hard Rule was broken.

**Step 3: Look at the preview yourself.** Check that:

- Letters don't touch or crash
- Everything sits on a common baseline, with descenders below it
- Stroke weight is even from letters to numbers to symbols
- No stray specks
- The OTF and TTF render the same

Fix what you find, rebuild, and check again before sending. Include the side-by-side comparison from Step 2 with your delivery so the user can see it too.

### 2.12 Deliver

- Send 4 separate files (never zipped): `[Font Name].otf`, `[Font Name].ttf`, `[Font Name] Preview.png` and `[Font Name] Comparison.png` (the side-by-side from 2.11)
- Show the pass/fail check table from 2.11 in your reply
- Summarize in plain language: what came from the sheet, what you built or fixed, and anything the user should know (for example, "texture prints as 1 solid color" or "curves will look soft at very large sizes because the sheet was small")
- Invite fixes in plain English.

---

## Part 3: What You Get Back

- **An .otf file:** use this one in Adobe apps, Affinity, CorelDRAW, Office and Canva
- **A .ttf file:** use this one for older programs and embroidery software that only read TrueType
- **A preview image:** your font typed out so you can check it before installing
- **A comparison image:** your original art next to the finished font, row by row, so you can spot anything that changed

**What's built in, even if your art didn't have it:**

- **Accented letters** for names like José, Peña, Zoë and Müller, plus ¿ and ¡
- **Spacing by shape**, so round and straight letters look evenly spaced
- **Tabular numbers** you can turn on so prices line up in columns (see Part 6)
- **Kerning** for tight pairs like AV, To and LT

---

## Part 4: Review the Preview

Look at the preview like a customer proof:

- Do any letters touch?
- Does anything float above or sink below the line?
- Do the numbers and symbols look as heavy as the letters?
- Is anything missing that you'll need on a job?
- Does it look like your sheet?

---

## Part 5: Asking for Fixes

Just say what you see. Examples that work:

- "The letters are touching. Space them out a little."
- "The $ and & look too bold next to the letters."
- "The numbers look too small."
- "There's a speck above the w."
- "Make the lowercase g sit lower."
- "Add a ¢ sign that matches."
- "Make a solid version without the texture for embroidery."
- "Rename it [New Name]."
- "The O and C look too far from their neighbors. Tighten the round letters."
- "The accent on the É is too close to the letter."
- "Add Polish and Czech accents too."
- "Here are 2 more sheets with the lowercase and the numbers. Add them to the font."
- "This is the Thin weight of [Family Name]. Group it with the Regular I built before."

---

## Part 6: Install Your Font

**Mac**

1. Double-click the `.otf` file.
2. Font Book opens and shows a preview. Click **Install**.
3. Quit and reopen your design apps.

**Windows**

1. Right-click the `.otf` file.
2. Click **Install for all users** (or **Install**).
3. Close and reopen your design apps.

**Canva**

Canva's paid plans let you upload fonts through your Brand Kit. Upload the `.otf` file there.

**Embroidery software**

Install the `.ttf` file the same way, then check your software's instructions for TrueType fonts.

**Turning on tabular numbers (for price columns)**

- **Illustrator and InDesign:** select the text, open the OpenType panel, and choose **Tabular Lining** from the figure style menu.
- **Word:** select the text, open Font, then the **Advanced** tab, and set Number spacing to **Tabular**.
- **Canva:** OpenType number settings aren't available, so you'll see the default numbers.

**Font families**

If you built more than 1 weight of the same design, uninstall any older separate versions first. Then install the new files. They'll show up as 1 font with a style menu.

---

## Part 7: Test It Before a Real Job

- [ ] Type your shop name
- [ ] Type a price, a date and a phone number
- [ ] Type names with accents, such as José Peña and Zoë Müller
- [ ] Set a column of prices with tabular numbers turned on and check that the decimals line up
- [ ] Type a sentence with punctuation and quotes
- [ ] Set it huge for a headline and small for a caption
- [ ] Print it at actual size
- [ ] Screen printing: check that thin lines hold at the size you'll print. Burn a test screen if it's a thin weight.
- [ ] Embroidery: run a sew-out. Textured or very thin fonts may need a solid or heavier version.
- [ ] Textured fonts print as 1 solid color. Plan your separations around that.

---

## Part 8: Who Owns It?

- Make sure you own the rights to the art you upload. If an AI image tool made it, check that tool's terms for your plan before you use or sell anything made with the font.
- Don't ask the AI to copy an existing commercial font. Start from your own original art.
- Using your font in your own designs is the safest use. If you plan to sell or give away the font file itself, talk to an attorney first.

---

*Questions about using custom fonts in your shop's branding or design work? Visit marshallatkinson.com.*
