PicaJet

Reference Formats

SRW

SRW is Samsung's proprietary raw format, introduced with the NX10 mirrorless camera in 2010, now an orphaned format since Samsung exited the camera business.

Extension

.srw

Full name

Samsung RAW

Introduced

2010, with the Samsung NX10

Vendor

Samsung

What is inside the container

SRW is a TIFF/EXIF-based container storing unprocessed Bayer sensor data plus Samsung maker-note metadata and an embedded JPEG preview. Samsung's own raw-conversion software (bundled utilities tied to the NX line) is no longer maintained, so ongoing support depends entirely on third parties such as Adobe and the open-source libraw project. This makes SRW one of the more clearly at-risk formats in this list from a pure DAM-longevity standpoint.

How to open it

Windows / macOS Adobe Camera Raw or Lightroom Classic, via Adobe's camera raw plugin update for supported NX models
Cross-platform, open source RawTherapee or darktable, both decoding SRW through libraw
Batch conversion Adobe DNG Converter, useful for normalizing SRW libraries since Samsung's own software is discontinued
Legacy Samsung native Samsung's bundled NX-series raw converter, still usable but unsupported and unmaintained

For archives

SRW should be treated as a priority conversion candidate for any DAM. Samsung discontinued its NX camera line and exited the standalone camera market, so there is no active vendor maintaining raw-decoder compatibility going forward; converting SRW masters to DNG now, while Adobe and libraw still support current camera models, avoids relying on aging third-party decoders indefinitely.

Samsung introduced SRW alongside the NX10, its first NX-series mirrorless camera, which launched in January 2010 with a 15-megapixel APS-C sensor and the new Samsung NX lens mount. SRW files use a TIFF/EXIF-based structure typical of raw formats from that era, storing the camera’s raw Bayer sensor output together with an embedded JPEG preview and Samsung-specific metadata fields.

What sets SRW apart from the other manufacturer raw formats in this reference series is that Samsung is no longer an active camera manufacturer: the company wound down its NX camera line and exited the standalone camera business in the mid-2010s. That leaves SRW support permanently in the hands of third parties — Adobe’s Camera Raw team and the open-source libraw project — with no vendor left to fix decoding issues on new discoveries about older camera models.

That orphaned status is exactly the scenario DNG was designed to protect against, and it is the clearest practical argument in this whole set of formats for proactive conversion: a DAM holding SRW assets from discontinued Samsung NX cameras gains real insurance by converting to DNG now, rather than waiting for a future software update that may never come.

Frequently asked

Why is SRW flagged as a priority conversion candidate for a DAM?

Samsung discontinued its NX camera line and exited the standalone camera market, so there is no active vendor maintaining raw-decoder compatibility going forward, making SRW one of the more clearly at-risk formats for long-term DAM support.

Is Samsung's own SRW conversion software still maintained?

No longer maintained. Samsung bundled a rebadged Silkypix Developer engine with NX cameras as its own RAW/SRW converter, but after Samsung exited the standalone camera business around 2015-2016 and discontinued the NX line, that software stopped receiving updates and is no longer distributed through official channels. Any copy still running today is unsupported legacy software with no compatibility guarantees for newer operating systems, so archives relying on it should not treat it as a durable long-term dependency.

What should a DAM do with SRW masters now?

Convert SRW masters to DNG while active third-party support still exists, rather than keeping them raw indefinitely. Adobe Camera Raw/Lightroom Classic, RawTherapee and darktable (via libraw) currently decode SRW reliably, but with Samsung gone from the camera market, that support is maintained by the open-source and Adobe ecosystems rather than the format's original vendor. Migrating now, while multiple independent decoders still agree on interpretation, is safer than waiting until support narrows to a single tool.

What does SRW's container structure look like?

SRW is a TIFF/EXIF-based container, not a bespoke binary format. The full-resolution Bayer sensor data sits in a sub-IFD nested inside the first TIFF IFD, alongside Samsung maker-note metadata, a thumbnail, and - notably - a complete full-resolution embedded JPEG preview, so an SRW file effectively bundles a JPEG and a RAW together. Early NX models store raw samples as uncompressed, big-endian, packed 12-bit values; some later NX bodies needed an updated decoder (LibRaw's Samsung v3 decoder) to read correctly.

When was SRW introduced?

SRW debuted in 2010 alongside the Samsung NX10, the company's first NX-series mirrorless camera and its entry into APS-C mirrorless systems. It remained Samsung's raw format across the NX line's roughly five-year lifespan, through models like the NX1 and NX500, until Samsung wound down NX production and exited the standalone camera business around 2015-2016, leaving SRW without further first-party camera releases to extend its use.

What tools currently decode SRW?

Adobe Camera Raw and Lightroom Classic support SRW directly, as do the open-source raw processors RawTherapee and darktable, both built on the libraw decoding library. libraw itself can also be used standalone or embedded in other software. Coverage spans the NX camera range, though some newer bodies needed a decoder update (LibRaw's Samsung v3 decoder, which addressed files such as the NX500) to read correctly, so current libraw/ACR versions are worth confirming before relying on older toolchains.

Is Samsung's legacy NX-series raw converter usable today?

It can still technically run on some systems, but it is unsupported, unmaintained legacy software - a rebadged Silkypix Developer build Samsung bundled with NX cameras and stopped updating once it exited the camera business. It was never guaranteed to work on current operating systems, receives no security or compatibility patches, and depending on it for an active archive workflow is riskier than using presently maintained tools like Adobe's converters or libraw-based applications.

What's the practical batch-conversion path for a SRW-heavy legacy collection?

Adobe DNG Converter is the standard batch path: point it at a folder tree of SRW masters and it processes them in bulk into DNG, preserving the raw sensor data while standardizing the container into a widely supported, vendor-neutral format. For a large legacy NX collection, this converts the whole archive in one pass without touching Samsung's discontinued software, and the resulting DNGs stay readable by Adobe tools, RawTherapee, and darktable long after any single decoder's SRW support might lapse.

Sources