Jetformat

Inspect fonts, EMF images, and XMP metadata

Utility commands for fonts, EMF images, and XMP metadata. All free.

By Jetformat

Font inspection, EMF rasterization, and XMP inspection are file utilities for checking document assets before conversion. Jetformat exposes them as font, emf, and xmp resources; these utilities are free and do not require a signed-in account.

Choose the command by the asset you actually have. A missing font, a vector illustration, and a metadata packet are different inputs and need different checks.

Choose the right asset command

Input and question Command Result to inspect
TTF or OTF: what font is this? font info Font information
TTF or OTF: can it be read? font validate Validation result
TTF or OTF: keep selected characters? font subset runes A new font file
EMF: make a raster preview? emf to-png PNG image
Media file or XMP sidecar: what metadata exists? xmp info Metadata properties

Check a font before using it

  1. Run font info against the exact font file you intend to supply.
  2. Run font validate before rewriting or subsetting it.
  3. Save any changed font to a separate output path and validate that output.
  4. Convert a representative document with the intended font directory, then inspect the resulting page images. A structurally readable font does not by itself prove correct line wrapping or glyph coverage.

font

jetformat font info font.ttf
jetformat font validate font.ttf
jetformat font rewrite font.ttf -o rewritten.ttf
jetformat font subset runes font.ttf "中文ABC123" -o subset.ttf
jetformat font subset gids font.ttf 1 2 3 -o subset.ttf

Subsetting by runes keeps only the glyphs for the given characters, which shrinks fonts embedded in PDFs.

emf to-png

jetformat emf to-png diagram.emf
jetformat emf to-png diagram.emf -o diagram.png --force

xmp info

jetformat xmp info photo.jpg --paths
jetformat xmp info sidecar.xmp

Reads standalone XMP or XMP embedded in media files.

Character subsets versus glyph IDs

Use subset runes when the required text is known. In the example above, 中文ABC123 supplies 8 characters; it is an illustrative input, not a promise that the result contains exactly 8 glyphs. Shaping and font internals can require more than one glyph for text. Do not assume a smaller file is suitable for documents that introduce additional characters later.

Use subset gids only when the glyph IDs are known for that exact font. The example requests 3 glyph IDs: 1, 2, and 3. IDs from another font are not interchangeable. Keep the original font and check the output with the strings the downstream document will actually use.

Inspect an EMF preview and XMP fields

A PNG preview lets you check an EMF drawing visually; it is a raster derivative, not an editable vector replacement. Compare linework, labels, transparency, and the image boundary against the source application where available.

XMP is a metadata format. Reading it does not remove metadata or prove that a media file has no other identifying information. Use --paths when you need the property locations, and inspect the returned fields before deciding which belong in a published asset.

The Microsoft OpenType overview describes the font format, while Adobe XMP documentation explains the metadata standard. These describe formats, not a guarantee that every feature is supported by Jetformat. See font inspection, font validation, and XMP inspection for focused tasks.

Last updated