PFB to PFM Converter

Generate PFM metrics from PFB fonts — online, free

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

Complete Font Pairing

Generate the PFM metrics file your PFB font needs for proper installation and text rendering on Windows systems.

Accurate Metrics

Width tables, kerning pairs, and encoding data are precisely extracted to ensure correct typographic spacing in all applications.

Cloud-Based Extraction

Metric extraction happens on our servers — no need to install FontForge or other specialized font tools on your machine.

How to convert PFB 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

PFB (Printer Font Binary) is the compact binary representation of Adobe's PostScript Type 1 font format, introduced alongside PFA in 1984. Where PFA stores the entire font program as hex-encoded ASCII text, PFB wraps the same data in a lightweight binary container that uses segment headers to mark regions as ASCII or binary. The encrypted glyph outline section (eexec) is stored as raw bytes rather than hex characters, cutting the file size roughly in half compared to PFA. Each segment begins with a marker byte and a 32-bit length field, making the format simple to parse while still significantly more compact. PFB became the dominant Type 1 distribution format on Windows and DOS platforms, used in combination with PFM (Printer Font Metrics) or AFM files that supply the character width and kerning data needed for text layout. One advantage is storage and transfer efficiency — the binary encoding means a typical text font occupies 30-50 KB rather than the 60-100 KB its PFA equivalent would require. The segmented structure also allows PostScript interpreters to stream font data efficiently, processing ASCII and binary portions with their respective handlers. Adobe Type Manager (ATM) on Windows relied on PFB files to render smooth Type 1 text on screen, a capability that transformed desktop publishing on the PC platform. While OpenType fonts have largely replaced Type 1 for new work, PFB files persist in established print workflows, archival font libraries, and systems that depend on PostScript output.
Developer: Adobe Systems
Initial release: 1984
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 PFB to PFM?

Windows requires a PFM companion file alongside PFB to properly install Type 1 fonts. Generating PFM restores missing width, kerning, and encoding data.

How to open PFM?

PFM files are used by Windows internally. You can inspect them with font utilities like FontForge or Adobe's Type Manager, but they aren't meant to be opened directly.

What data does the PFM contain?

PFM stores character widths, kerning pairs, font encoding, and metrics that applications need for precise text layout and spacing.

Is PFM necessary if I already have AFM?

On Windows, yes — most Windows apps expect PFM for Type 1 fonts. AFM serves a similar role but follows a different specification used primarily on other platforms.

Can I process a batch of PFB files?

Absolutely. Upload multiple PFB fonts and generate all corresponding PFM files in a single batch conversion session.

PFB to PFM Quality Rating

4.4 (78 votes)
You need to convert and download at least 1 file to provide feedback!