T11 to PFM Converter

Extract Windows font metrics from CID Type 2 fonts as PFM online

Drop files here. 1 GB maximum file size or Sign Up
to
Facebook Amazon Microsoft Tesla Nestle Walmart L'Oreal

Windows Metrics

PFM provides the metric data Windows needs to properly render and space your T11 font — essential for Type 1 font installation on Windows.

Paired Output

Generate a PFM from your T11 CID Type 2 font to complement a PFB file — together they form a complete Type 1 font installation package for Windows.

Confidential

Your T11 font is deleted after conversion and PFM outputs are removed within 24 hours — no residual data on our servers.

How to convert T11 to PFM

1

Select files from Computer, Google Drive, Dropbox, URL or by dragging it on the page.

2

Choose pfm or any other format you need as a result (more than 200 formats supported)

3

Let the file convert and you can download your pfm file right afterwards

About formats

T11 (Type 11) is a PostScript font type defined by Adobe Systems as part of the CID-keyed font architecture, combining CID glyph addressing with TrueType outline data wrapped in a Type 42 PostScript shell. In Adobe's font type numbering, Types 9, 10, and 11 are CID-keyed counterparts to Types 1, 3, and 42 respectively — so Type 11 is essentially a CID-keyed Type 42, designed for TrueType fonts that contain very large glyph sets, particularly CJK (Chinese, Japanese, Korean) character collections. The format allows PostScript interpreters with TrueType rasterizer support to render CJK TrueType fonts while using CID numeric indexing instead of glyph names, which is critical for character sets numbering in the tens of thousands. Glyph outlines remain in native TrueType quadratic spline format, preserving the original hinting instructions, while the CID layer provides efficient glyph access and subsetting through CMap resources. One advantage is direct TrueType rendering quality — unlike converting TrueType outlines to PostScript cubics, Type 11 passes the original outlines to the rasterizer intact, preserving hand-tuned grid-fitting instructions. The CID indexing provides another benefit by supporting multiple encoding schemes (Unicode, national standards) mapped to the same glyph collection without data duplication. Type 11 fonts appear primarily in professional CJK print production and PDF document workflows where large TrueType-based character sets must be embedded in PostScript-derived output.
Developer: Adobe Systems
Initial release: 1993
PFM (Portable Float Map) is a floating-point raster image format devised by Paul Debevec around 2001, designed to store high-dynamic-range image data with the simplicity of the Netpbm family of formats. PFM extends the PBM/PGM/PPM philosophy — minimal header, raw data, no compression — to 32-bit IEEE floating-point samples, providing direct access to HDR pixel values without the encoding overhead of formats like OpenEXR or the limited range of Radiance HDR's RGBE encoding. The file structure is deliberately minimal: a two-character magic number ('Pf' for grayscale, 'PF' for color), width and height on the next line, a scale/endianness indicator (negative for little-endian, positive for big-endian, with magnitude indicating scale factor), and then the raw 32-bit float data for each pixel. PFM files store one float per pixel for grayscale or three floats (RGB) per pixel for color, with no compression, alpha channel, or metadata support. The format emerged from the HDR imaging research community where Debevec's work on image-based lighting and light stage capture required a simple, unambiguous way to store linear floating-point radiance values that could be easily exchanged between research tools. One advantage is absolute simplicity for HDR data: PFM can be read and written in a few lines of code in any language that supports IEEE floats, with no library dependencies — ideal for research prototyping and quick data exchange between custom tools. The format's widespread adoption in the computer vision and computational photography research community is another practical strength — optical flow benchmarks (Middlebury), depth estimation datasets, and radiance field captures commonly use PFM. The format is supported by ImageMagick, OpenCV, HDR Shop, and Luminance HDR.
Developer: Paul Debevec
Initial release: 2001

Frequently Asked Questions

Why convert T11 to PFM?

PFM provides Windows-specific font metric data needed to pair with PFB files. Converting T11 to PFM enables proper font installation on Windows systems.

How do I open a PFM file?

PFM files are used internally by Windows alongside PFB font files. Font management tools and Type 1 font installers read PFM metrics data.

Do I need both PFM and PFB?

Yes — on Windows, PostScript Type 1 fonts require both the PFM metrics file and the PFB outline file to function properly as an installed font.

What data does PFM contain?

PFM stores character widths, kerning pairs, and font metadata in a Windows-specific binary format — parallel to what AFM provides in a cross-platform way.

Is T11 to PFM free?

Yes — Convertio handles this conversion completely free in the cloud. No software or signup needed.