PowerPoint Font Finder
Find hidden, phantom, theme, master, and layout fonts in PPTX presentations, then build a verified replacement copy locally in your browser.
About this powerpoint font finder
Standard PPTX · file < 100 MB (100000000 bytes) · scan first, replace only explicit mappings. This changes stored references, not installed fonts or rendered glyph metrics. Legacy PPT, PPTM, encrypted and signed presentations are excluded; inspect the downloaded presentation before reuse.
PowerPoint can report a font that is not visibly used on any slide, refuse to replace it, or warn that some fonts cannot be saved with the presentation. The reference may live in a slide master, layout, notes master, chart, theme, bullet definition, empty text level, East Asian setting, complex-script setting, or an object inherited through several relationships. This scanner reads the PPTX package directly so those stored references become visible before any change is made.
What the scanner actually measures
The report enumerates typeface references stored inside PPTX XML. It distinguishes literal family names such as Arial or Avenir from theme tokens such as +mj-lt and +mn-lt. Each record lists the character channel—Latin, East Asian, complex script, symbol, bullet, or theme script—the package parts containing it, and the slide numbers potentially affected through layout, master, theme, chart, or notes relationships.
Worked hidden-font example
A presentation visibly uses Aptos, but PowerPoint still lists Helvetica Neue in Replace Fonts and refuses to remove it. The scan finds Helvetica Neue in an East Asian font element inside a custom slide layout inherited by slides 4, 7, and 12.
You explicitly map Helvetica Neue to Aptos. CZOA changes only matching literal typeface attributes, rebuilds a separate _font-fixed.pptx, reopens the package, and runs the same complete scan again before enabling the download.
Why “phantom font” is a useful symptom, not a file type
PowerPoint does not define a formal phantom-font object. Users apply the name to several different situations: an invisible style reference, an uninstalled font, a theme mapping, an embedded font declaration, an alternate language font, or text converted into artwork. The scan reports the stored evidence and its source instead of collapsing every case into one diagnosis.
Parts inspected
- Slides, slide layouts, slide masters, presentation defaults, themes, table styles, notes slides, notes masters, and handout masters.
- Charts and SmartArt/diagram XML stored within the presentation package.
- Latin, East Asian, complex-script, symbol, bullet, and theme-script typeface attributes.
- Presentation relationships are followed backward so a master or theme reference can list the slides it may affect.
- Embedded font binaries are counted but never extracted, published, or deleted because font files can carry licensing restrictions.
What the browser cannot prove
A normal webpage cannot reliably enumerate every font installed on Windows or macOS. Browser font checks can be affected by permissions, privacy protection, font activation software, fallback behavior, and whether the browser has already loaded a face. For that reason, CZOA does not mark a stored name “installed” or “missing.” Verify availability in the destination desktop environment or through your organization's licensed font manager.
Controlled replacement safety
Replacement is never automatic. You choose each old family and type the exact new family. Theme tokens are scan-only because converting a major/minor theme token into a literal family can change inheritance across the deck. CZOA does not edit binary embedded objects, delete embedded fonts, open OLE workbooks, or rewrite vector artwork. The original file stays untouched, a separate PPTX is produced, and a JSON manifest lists every mapping, changed part, count, exclusion, and creation time.
Why desktop PowerPoint review is still required
A structurally valid PPTX can still look different after a font change because typefaces have different metrics, line heights, glyph coverage, kerning, weights, and fallback behavior. Open the generated copy in the exact Windows or Mac PowerPoint version used by the audience. Check titles, tables, charts, equations, non-Latin text, speaker notes, clipped text, animations, and brand templates before replacing a production presentation.
Troubleshooting common PowerPoint font warnings
- Some of your fonts cannot be saved: scan for stored literal names, inspect embedded-font declarations, and confirm the font's embedding license in desktop PowerPoint.
- Replace Fonts does nothing: inspect East Asian, complex-script, bullet, layout, master, and theme locations. A visible slide text box may not be the source.
- Font looks correct on one computer only: confirm that the exact family and weight are installed or legally embedded on the destination device.
- Old font remains after replacement: rescan the generated copy. Remaining theme tokens, OLE contents, vector artwork, or embedded font declarations may be outside literal replacement.
- Text wraps or clips after replacement: this is a visual metric change, not package corruption. Choose a metrically compatible font or adjust the affected placeholders in PowerPoint.
ECMA-376 Office Open XML · PowerPoint Font Finder verification · Audit standards
How to use it
- Choose a standard PPTX file. The tool validates package structure and scans all supported presentation XML without changing the source.
- Review literal fonts, theme tokens, reference channels, package locations, and potentially affected slides. Do not interpret a stored reference as proof that the font is installed.
- Add one or more explicit old-font to new-font mappings. Confirm the reference count and read the exclusions before building a copy.
- Build the verified copy, download the PPTX and change manifest, then open the result in desktop PowerPoint on each target platform for a visual review.
Frequently asked questions
Is the PowerPoint file uploaded?+
No. Package validation, scanning, replacement, rebuilding, and verification run locally in the browser. CZOA does not intentionally transmit or retain the presentation bytes.
Can this prove which fonts are installed on my computer?+
No. Browser font enumeration is not authoritative. The report identifies stored PPTX references. Check installation and licensing in the destination operating system or font manager.
Why is a font listed when no visible text uses it?+
It may be stored in a master, layout, theme, bullet rule, empty list level, notes part, chart, East Asian setting, complex-script setting, or embedded-font declaration.
Does replacement guarantee every font problem is fixed?+
No. It changes explicitly selected literal XML typeface references. Theme remapping, OLE contents, EMF/WMF artwork, embedded font binaries, font licensing, unavailable glyphs, and visual reflow need separate review.
Are PPTM, encrypted, or signed presentations supported?+
They are not rewritten. Save a separate standard PPTX copy first. Repackaging a macro-enabled or digitally signed file could invalidate code or signatures, so the tool refuses that risk.
Why must I review the output in PowerPoint?+
Different fonts have different metrics and glyph coverage. Package validation proves that the rebuilt PPTX is structurally readable and that references changed; it cannot prove every slide still fits or renders identically on every device.