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.
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.
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.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.
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.
| Aspect | Samsung RAW (.srw) | Portable graymap (.pgm) |
|---|---|---|
| Format type | Lossless — every pixel or sample is preserved exactly | Lossless — every pixel or sample is preserved exactly |
| How it stores data | tIFF-based container with Samsung-specific tags around 12- and 14-bit Bayer mosaic data | p2 stores samples as whitespace-separated ASCII integers; P5 stores them as raw bytes |
| Strongest at | reprocessing photo libraries shot on NX-system cameras | machine vision and image-processing pipelines that operate on intensity alone |
| Weak spot | the format is abandoned: no vendor updates, no new hardware, dwindling attention | uncompressed, so files are large relative to PNG for the same data |
| Metadata | standard EXIF and Samsung MakerNotes are embedded and still parsed correctly by ExifTool and major raw engines; XMP lives in sidecars written by editors | none 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 |
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.
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.
Press Convert. A LibRaw WebAssembly decoder demosaics the sensor data in your browser and renders a developed image ready for export.
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.
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.
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.
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.
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.
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.