Verified local conversion

SRW to PGM

Developing a .srw camera file into .pgm turns unprocessed sensor data into a finished image any app can open. Free, private, and validated — the file never leaves your browser.

Private for supported formats — processed in your browser

Convert supported files

Runs on your device

Drop SRW files here

Batch files can each use a different output. Nothing uploads for local conversions.

Working inputs include camera RAW, browser-local audio/video, PDF, CBZ/CBR comics, office documents, ebooks, markup, 3D models, structured text, images, and archives.

About converting Samsung RAW to Portable graymap

Developing a .srw camera file into .pgm turns unprocessed sensor data into a finished image any app can open. An .srw file is a Samsung RAW photograph from the company's NX-series mirrorless cameras and a few compacts, produced only during Samsung's 2010-2015 push into dedicated cameras. Because Samsung exited the camera business, .srw is now an orphaned format: existing files remain readable, but no new cameras will ever create them.

A .pgm file is a Portable Graymap: a single-channel greyscale image storing one intensity value per pixel, with the maximum value declared in the header. It is the middle rung of the Netpbm ladder — richer than a one-bit bitmap, simpler than a colour pixmap. For this route the practical draw is raw samples in a declared range — no codec, no colour management, nothing to misinterpret and supports 16-bit depth, which most consumer formats do not — balanced against uncompressed, so files are large relative to PNG for the same data, which is worth knowing before you commit a large batch.

Why convert SRW to PGM?

The practical trigger for this conversion is usually a mismatch: with .srw, the format is abandoned: no vendor updates, no new hardware, dwindling attention. Switching to .pgm buys you raw samples in a declared range — no codec, no colour management, nothing to misinterpret, which is why it is the better fit for machine vision and image-processing pipelines that operate on intensity alone. Because the conversion runs locally, trying it costs nothing but a few seconds of compute on your own machine.

SRW vs PGM at a glance

AspectSamsung RAW (.srw)Portable graymap (.pgm)
Format typeLossless — every pixel or sample is preserved exactlyLossless — every pixel or sample is preserved exactly
How it stores datatIFF-based container with Samsung-specific tags around 12- and 14-bit Bayer mosaic datap2 stores samples as whitespace-separated ASCII integers; P5 stores them as raw bytes
Strongest atreprocessing photo libraries shot on NX-system camerasmachine vision and image-processing pipelines that operate on intensity alone
Weak spotthe format is abandoned: no vendor updates, no new hardware, dwindling attentionuncompressed, so files are large relative to PNG for the same data
Metadatastandard EXIF and Samsung MakerNotes are embedded and still parsed correctly by ExifTool and major raw engines; XMP lives in sidecars written by editorsnone beyond header comments. No colour profile, no EXIF, no acquisition metadata — anything an instrument recorded alongside the pixels has to travel in a separate file
01

Add your SRW file

Drop one or more .srw files onto the converter above, or browse for them. They load into browser memory only — nothing is uploaded, so there is no size-based pricing and no server queue.

02

Pick PGM as the output

Select .pgm in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if PGM is selectable, the route is real and validated.

03

Convert on your device

Press Convert. A LibRaw WebAssembly decoder demosaics the sensor data in your browser and renders a developed image ready for export.

04

Verify and download

Each result is signature-checked before the download unlocks, so a failed encode can never masquerade as a valid PGM file. Outputs keep the original filename with the .pgm extension.

SRW to PGM questions, answered

Will converting SRW to PGM lose quality?

Since srw is lossless-oriented and pgm is lossless-oriented, the conversion preserves the source content exactly as stored; no additional compression pass is applied beyond what .pgm itself requires.

Is it private to convert SRW files here?

Yes — the .srw file is processed inside your browser tab and never uploaded. A LibRaw WebAssembly decoder demosaics the sensor data in your browser and renders a developed image ready for export. Close the tab and the file is gone from memory.

Where will the PGM file work?

Standard in scientific and machine-vision toolchains — OpenCV, ImageMagick, MATLAB and Netpbm all read it — and absent from consumer software and browsers. Novus Convert decodes both ASCII and binary PGM locally, honours the declared maximum value when scaling to 8-bit output, and converts to the standard raster formats.

Will the PGM file be bigger or smaller than my SRW?

It depends on the content: p2 stores samples as whitespace-separated ASCII integers; P5 stores them as raw bytes. Convert one representative file first and compare before batch-processing a large set.

What happens to the metadata in my SRW file?

In .srw, standard EXIF and Samsung MakerNotes are embedded and still parsed correctly by ExifTool and major raw engines; XMP lives in sidecars written by editors. Re-encoding through the browser pipeline does not carry embedded metadata into the output, which doubles as a privacy scrub — check the exported file if you specifically need tags preserved.