BIN to PFM Converter

Create PFM floating-point images from MacBinary fonts

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

Float Precision

PFM captures pixel data with 32-bit floating-point accuracy. BIN to PFM conversion creates high-precision output for technical use.

Remote Processing

Convertio handles the BIN to PFM rendering on its own servers. Your hardware resources are not consumed during the conversion.

Secure Pipeline

Uploaded BIN files are deleted right after conversion. PFM output files are automatically removed within 24 hours.

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

BIN refers to MacBinary-encoded font files, a transfer format that preserves classic Macintosh file system features when moving data across platforms. Classic Mac OS stored fonts using the resource fork — a secondary data stream invisible to non-Mac systems — which meant that simply copying a Mac font to a Windows PC or Unix server would strip the actual font data entirely. MacBinary solves this by combining both the data fork and resource fork into a single flat file with a 128-byte header containing the original HFS metadata. In the font context, BIN files typically wrap TrueType suitcase fonts, PostScript Type 1 LWFN outline files, or bitmap NFNT font resources. The format was first specified in 1985 by Dennis Brothers and collaborators from the early Mac community, with MacBinary II following around 1987 and MacBinary III arriving in 1996 to support longer filenames. A key advantage is lossless preservation: every byte of the original Mac font file survives intact through email, FTP, or cross-platform file sharing, including creator and type codes that identify the font format. The single-file packaging is another practical strength — rather than dealing with separate data and resource streams, users and automated systems handle one portable container. Although modern macOS has moved away from resource forks and Mac fonts now typically ship as OTF, TTF, or DFONT files, BIN remains important for accessing archived font collections from the classic Mac era.
Developer: Dennis Brothers
Initial release: 1985
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 BIN to PFM?

PFM stores pixel data as floating-point numbers — ideal for HDR workflows, scientific imaging, and applications needing high precision.

How to open PFM files?

PFM files work with ImageMagick, GIMP, and HDR/scientific imaging tools that support the Portable Float Map specification.

What precision does PFM offer?

PFM uses 32-bit floating-point values per channel, providing much greater dynamic range and precision than standard 8-bit formats.

Is BIN to PFM conversion fast?

Very fast — font files are lightweight, and Convertio cloud servers deliver the PFM result in just a few seconds.

Is registration required?

No — Convertio provides free BIN to PFM conversion without any account creation or signup process.