Skip to content

PFM to WebP Converter

Convert PFM to WebP in your browser. PFM files usually come from computer vision benchmarks (the Middlebury stereo disparity maps, for example), HDR research and renderers; WebP is the better fit for images on websites and in apps. You get a lossy WebP at the quality you choose (lossless under More options), keeping transparency. Nothing is uploaded.

  • Processed locally
  • No upload, no wait
  • No sign-up
  • No watermark

Drop images here

or choose files · paste with Ctrl/⌘ V

PFM expected · other image formats also work

Files are processed on this device. Nothing is uploaded.0 B uploaded

How to use PFM to WebP

  1. 1

    Add your PFM files: drop them here, choose them, or paste from the clipboard.

  2. 2

    Set the quality. 80 to 85 is visually close to the original for most photos.

  3. 3

    Click Convert. Each file is decoded and encoded in a background thread on this device.

  4. 4

    Download the .webp files one at a time or together as a ZIP.

Why use Aback Images for pfm to webp

Where the WebP goes next

WebP opens in every current browser, Windows, macOS, Android, and recent Photoshop, GIMP and Affinity.

WebP next to PFM

A lossy WebP usually comes out far smaller than the PFM, which stores none.

The first lossy pass

The PFM holds 32-bit floating point per channel with nothing discarded yet. This conversion is the first lossy encode these pixels see, and hard edges and flat colour show it first.

Processed on your device

Your images are decoded, edited and encoded inside this browser tab by Web Workers. Nothing is uploaded to a server.

PFM vs WebP

What changes from PFM to WebP

Encoding: the PFM uses none; WebP uses lossy VP8 coding or lossless VP8L, and the download is a lossy WebP at the quality you choose (lossless under More options), keeping transparency.

Bit depth: 32-bit floating point per channel in the PFM; WebP allows 8 bits per channel, and the WebP written here has 8 bits per channel. Float values are mapped to 8 bits per channel, and values above 1.0 clip.

Colour: RGB ('PF') or greyscale ('Pf'), in linear values in the PFM; WebP supports RGB; lossy WebP stores colour at half resolution (4:2:0), written here as 8-bit sRGB.

Metadata: the PFM can carry none beyond the header; WebP can carry EXIF, XMP and ICC chunks, but nothing is copied across.

About PFM

PFM is a minimal floating-point image format in the Netpbm style: a three-line text header and raw 32-bit floats. Research code uses it for HDR images, disparity and depth maps.

A PFM file is the text 'PF' (colour) or 'Pf' (greyscale), the width and height, and a scale factor whose sign gives the byte order (negative means little-endian), then 32-bit floats with rows stored from the bottom of the image up.

PFM files usually come from computer vision benchmarks (the Middlebury stereo disparity maps, for example), HDR research and renderers.

About WebP

WebP is Google's web image format. It supports lossy and lossless compression, transparency and animation, and is typically 25 to 35 percent smaller than JPEG at the same visual quality.

A WebP is a RIFF file: 'RIFF', a length, 'WEBP', then chunks. A simple lossy file is one VP8 chunk and a lossless one is VP8L; the extended VP8X header announces alpha, animation, ICC, EXIF or XMP chunks.

When converting PFM to WebP makes sense

WebP is the better choice for images on websites and in apps, while PFM suits HDR research, depth and disparity maps.

WebP strengths: 25-35% smaller than JPEG; Transparency and animation in one format; Supported by every modern browser. Drawbacks to weigh: Some older desktop apps and photo printers cannot open it; Max 16383 px per side.

Limitations

  • PFM stores raw measurements: depth and disparity maps hold distances rather than colours, so the converted picture is a visualisation, not a photograph.
  • Values above 1.0 are clipped rather than tone-mapped.
  • A few older desktop apps, print services and upload forms still reject WebP; keep a JPG or PNG copy for those.
  • WebP images are limited to 16383 pixels on each side.

Frequently asked questions

Does converting PFM to WebP lose quality?

WebP is lossy, so detail the eye barely notices is discarded to save space. Float values are mapped to 8 bits per channel, and values above 1.0 clip.

What quality should I choose for WebP?

80 to 85 is visually close to the original for most photos. Go lower for thumbnails, or switch on Lossless under More options for screenshots and graphics.

Which apps open WebP files?

Every current browser, Windows, macOS, Android, and recent Photoshop, GIMP and Affinity.

Are my images uploaded anywhere?

No. Processing happens inside your browser with WebAssembly and Web Workers. The site only downloads the app code and codecs; your files never leave your device. You can confirm this with the live upload counter on the tool, or in your browser's network panel.

Can I process many files at once?

Yes. Drop a whole selection or folder. Files are processed in parallel on several worker threads, each result can be downloaded on its own, and everything can be saved as one ZIP.

Is it free? Is there a file limit or watermark?

It is free with no account, no watermark and no daily limit. The only limit is your device's memory: very large images (over roughly 100 megapixels) may be refused to keep the tab from crashing.