Keep Font Permission Records With the Publication Files

Inventory the fonts actually used in the manuscript and cover, link each to its source and applicable permission record, and review the intended publication use against that evidence. Keep technical font preparation separate from the question of whether the project has the needed rights.

Identify the fonts in the actual project

A manuscript may use one body font and several others in headings, decorative initials, diagrams, or cover artwork. Begin with the source files and final exports rather than relying on the designer's memory of the main typeface. Imported graphics and reused templates can introduce fonts that do not appear in the ordinary paragraph-style list.

Record the family, style, source, and location of each font where the tools make that information available. Distinguish the selected typeface from any replacement that appears after export or on another machine. The permission review needs to concern what the publication actually uses, not merely what the author originally intended to use.

Preserve the source and applicable terms

Keep the relevant acquisition record and terms with the project. A font found in a shared folder may lack the information needed to establish who supplied it and under what conditions. Ask the contributor for the appropriate record instead of treating availability on a computer as evidence of permission for every publishing use.

Retain the terms that apply to the actual acquisition or arrangement, with enough context to identify them. Do not rely only on a bookmark that may later lead to a changed page or a different product. This is a documentation step; interpreting uncertain conditions may require clarification from the provider or qualified advice suited to the situation.

Describe the intended uses precisely

List where the font will appear: print manuscript, cover, digital edition, promotional artwork, or another planned output. Also identify whether a workflow embeds font resources or otherwise uses them in a way relevant to the supplied terms. The review should compare actual intended uses with the applicable evidence rather than asking whether the font is generally allowed.

Avoid assuming that a contributor's ability to create an image settles every subsequent use of that image or its underlying resources. Keep the publication formats and distribution plans clear when seeking clarification. If the answer is incomplete, mark the specific use as unresolved instead of extending a narrow permission by inference.

Separate embedding checks from permission checks

KDP's paperback submission guidance includes technical font preparation requirements. Checking those requirements helps establish whether the file is prepared for printing. It does not independently establish the publisher's rights to use a particular font in the intended way.

Likewise, a permission record does not prove that the final export preserved the correct typeface or prepared it properly. Maintain both checks in the release process. One concerns the basis for use; the other concerns the actual file. Treating either as a substitute for the other leaves a gap that can remain invisible in an attractive page preview.

Review replacements as new decisions

If an unclear font is replaced, inspect the layout again. Different letter widths and spacing can change line breaks, page count, cover fit, and the appearance of symbols. A substitution that resolves a documentation problem can still create production changes requiring review across the affected files.

Update the inventory and retain a note about why the replacement occurred. Remove obsolete font dependencies from the active publication sources where appropriate, while preserving enough history to explain prior drafts. Confirm that imported graphics or alternate-format files have not retained the old typeface after the main manuscript was updated.

Check the final package against the inventory

Before approval, compare the manuscript, cover, and any relevant linked artwork with the font inventory. Confirm that each actual use has been reviewed and that open questions have a clear resolution. Keep the records accessible to the person responsible for the publication rather than leaving them only in a designer's private messages.

KDP's content guidance places responsibility for published material and rights with the publisher. A font record helps support that responsibility, but it is not a universal legal conclusion about every use. Complete the specific permission and technical checks, document the result for the final files, and revisit it when the edition or intended outputs change.