PFM to TAR Converter
Processing entirely on your device — large files may take a moment.
Portable Float Map and TAR Archive exist for different jobs: PFM (Portable Float Map) stores pixels as raw 32-bit floats — the lossless hand-off format for HDR pipelines, radiance research and render passes, riding the same family spirit as PBM/PGM/PPM. TAR preserves the exact file tree and permissions that Linux tooling expects.
Because the whole conversion happens on your device, it is instant, unlimited and genuinely private — no accounts, no watermarks, no files on anyone's server. Multiple files are converted in one go.
How PFM compares to TAR
| PFM | TAR | |
|---|---|---|
| Compression | None (raw floats) | None (pair with gzip/zstd) |
| Best for | HDR interchange, render passes | Linux packaging and source trees |
How to convert PFM to TAR
- 1
Select your files
Select your PFM file — it never leaves your device.
- 2
Convert instantly
The engine packs the file, byte for byte, into a TAR container — no re-encoding, no quality change.
- 3
Download results
Download the finished TAR archive.
About the PFM format
PFM (Portable Float Map) stores pixels as raw 32-bit floating-point values — no palette, no compression tricks, just the numbers. It belongs to the Netpbm family (PBM/PGM/PPM) and is the lingua franca for handing high-dynamic-range data between renderers, tone-mapping experiments and radiance research scripts.
Because the values are floats, a PFM can hold sunlight and candlelight in the same image without clipping. Viewers rarely open it directly: convert to PNG or JPG to get a tone-mapped preview of the same data.
+Strengths
- ✓Full floating-point precision
- ✓Dead-simple text/binary layout
- ✓Widely read by research tooling
!Limitations
- −Enormous files (16 bytes per pixel)
- −Almost no viewer support
About the TAR format
TAR (tape archive) is Unix's fifty-year-old answer to bundling: it concatenates files with headers into a single stream, preserving POSIX permissions, ownership and symlinks — but compressing nothing. It is the container half of the classic .tar.gz pairing and the native format of Linux source trees and backups.
Being pure bundling, TAR pairs with a compressor: gzip (the classic), bzip2, zstd. Alone, a TAR is the same size as its contents. Windows 10+ ships bsdtar, so even Windows can unpack it now — permissions aside, where NTFS has no room to be faithful.
+Strengths
- ✓Preserves Unix permissions and symlinks
- ✓Streamable: works over pipes and tapes
- ✓The standard of Linux distribution and backup
!Limitations
- −No compression by itself
- −No built-in encryption
- −Permissions meaningless on Windows filesystems
Why convert PFM to TAR?
Converting makes sense where the strengths of TAR meet what PFM cannot give you. Preserves Unix permissions and symlinks Meanwhile Enormous files (16 bytes per pixel) One pass through the converter above puts your file on the right side of that trade-off.
Frequently asked questions
Is this PFM to TAR converter really free?
Yes — completely free, with no sign-up, no watermark and no daily conversion limits. The site is supported by advertising.
Are my files uploaded to a server?
No. The conversion runs entirely inside your browser using WebAssembly, so your files never leave your device — that is what makes it instant and private.
Does it work on Windows, Mac, iPhone and Android?
Yes. Anything with a modern browser works: Windows, macOS, Linux, Android and iOS. No software installation is required.
Will I lose quality converting PFM to TAR?
No — TAR is a lossless format, so every pixel of the converted image matches your original PFM file. You can also adjust the quality/size balance before converting when the target format supports compression.
Will transparent areas survive the conversion to TAR?
Transparency is kept whenever TAR actually supports an alpha channel. If the target format has none (like JPG), transparent areas are flattened onto a white background — that is a property of the format, not of this tool.
What happens to EXIF data and other metadata?
Conversions here re-encode the image, and re-encoding generally does not carry the original metadata over. If the EXIF data of your PFM files matters (camera model, GPS, timestamps), keep the original file as the master and treat the converted copy as the shareable version.