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 .avif 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 .avif 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.
An .avif file stores a still image (or sequence) coded with the AV1 video codec inside a HEIF-derived container. It is currently among the most efficient image formats deployed on the web, routinely beating JPEG by half at similar quality while adding HDR, wide gamut, and alpha. For this route the practical draw is best-in-class compression among widely supported web formats and 10/12-bit HDR and wide-gamut color, which JPEG cannot represent — balanced against encoding is much slower than JPEG or WebP, especially at high effort settings, 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 .avif buys you best-in-class compression among widely supported web formats, which is why it is the better fit for serving hero images and photo galleries where bandwidth savings are significant. Because the conversion runs locally, trying it costs nothing but a few seconds of compute on your own machine.
| Aspect | Samsung RAW (.srw) | AVIF image (.avif) |
|---|---|---|
| Format type | Lossless — every pixel or sample is preserved exactly | Lossy — discards detail it judges invisible to shrink files |
| How it stores data | tIFF-based container with Samsung-specific tags around 12- and 14-bit Bayer mosaic data | encodes AV1 intra frames; both lossy and a mathematically lossless mode are defined |
| Strongest at | reprocessing photo libraries shot on NX-system cameras | serving hero images and photo galleries where bandwidth savings are significant |
| Weak spot | the format is abandoned: no vendor updates, no new hardware, dwindling attention | encoding is much slower than JPEG or WebP, especially at high effort settings |
| 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 | eXIF and XMP are stored as metadata items in the HEIF container alongside ICC profiles or CICP color signaling, and mainstream encoders preserve them on conversion |
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 .avif in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if AVIF 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 AVIF file. Outputs keep the original filename with the .avif extension.
Some. Since srw is lossless-oriented and avif is lossy-oriented, the encoder will discard detail it judges least visible; the quality slider controls how aggressive that is. Keep the original .srw if you may need a pristine master later.
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.
Chrome 85+ (2020), Firefox 93+ (2021), and Safari 16+ (2022) render AVIF natively, covering the overwhelming majority of current browsers. On the desktop, macOS 13+ and Windows (via the AV1 Video Extension) preview it, but plenty of older editing and printing software cannot open it yet.
Smaller, usually dramatically so — that is the main reason this route exists. The quality slider trades size against fidelity; the default sits at the point where most people cannot spot the difference.
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.