Find the fonts that can derail a file handoff.

What does the cross-format font inspector do?

Inspect a PPTX, DOCX, PDF, or SVG locally to inventory readable font references, internal names, subsets, and likely substitution risks. The immediate result is a local font inventory for the selected file. That makes the tool useful when a focused question needs an answer before a file is handed off, a campaign is trafficked, or a production workflow begins.

The scope is intentionally narrow. It is designed for understanding one file, font, or format-compatibility risk, not for replacing the complete production process. A useful result should make the next decision clearer while leaving the original file, design, or workflow under the user’s control.

Your files and inputs are processed locally in this browser and are not uploaded to Hypermatic. Local processing reduces unnecessary data exposure, but it does not remove the need to follow the privacy, confidentiality, and retention requirements that apply to the source material.

How should the cross-format font inspector be used?

Start with the same input that will be used in production whenever possible. Draft content, substitute files, and approximate dimensions can be useful during exploration, but the final check should use the actual export, final copy, destination, or supported range.

Work through the steps in order and keep the generated result beside the source. If the result identifies a warning, decide whether it is a real production problem, an acceptable tradeoff, or a limitation of a browser-based inspection before changing the underlying work.

• Choose the design, presentation, or document file being handed off.
• Inspect its XML or PDF source for readable font references and internal font names.
• Confirm availability, licensing, embedding, and approved fallbacks on the destination system.

How should the result be interpreted?

A browser tool can make measurable signals visible, but it cannot reproduce every application, platform, rendering engine, policy, or team constraint. Treat the report as evidence for a decision rather than a universal guarantee. The strongest verification is the exact converted file opened in the destination application and compared with the untouched source.

Pay particular attention to edge cases that are easy to miss during a quick check: unusual fonts, long or localized content, hidden metadata, external dependencies, different aspect ratios, browser-specific behavior, and last-minute source changes. Re-run the tool whenever the production input changes materially.

• A detected font name does not prove that the font is embedded.
• Subset prefixes and internal names can differ from the family name shown in an authoring app.
• Run an actual destination-app test after resolving the inventory.

Common questions about cross-format font inspector

Can the inspector tell whether every font is embedded? It can identify some package and PDF signals, but the primary result is a readable font-name inventory. Embedding and destination support still require format-specific verification.

Why might a font be missing from the report? The text may have been outlined, rasterized, compressed in an unsupported object stream, referenced through a theme, or stored under an internal name the lightweight scan does not recognize.

Is the cross-format font inspector free? Yes. You can use it without an account or signup. The focused result is generated directly in your browser.

When does Convertify become the better workflow?

The free tool is the right choice for a quick individual check, calculation, preview, or template. It remains useful even if the task only occurs once and no broader production workflow is needed.

Convertify becomes more practical when the same job turns into moving complete documents between Figma and supported design or presentation applications. At that point, keeping the work close to the Figma source reduces repeated exports, copy-and-paste steps, inconsistent decisions, and handoff drift.

Before adopting any workflow, compare the time spent on the recurring manual process with the setup and review required by the tool. The goal is not to add another application; it is to remove repetitive work while preserving the quality checks that still need human judgment.