Konversikan apa pun, dalam skala global.
200+ format dan API otomasi yang terasa instan.
CONVERT
Dari
Ke
Lepas file di sini atau pilih sumber
Unggah beberapa file sekaligus, campur format, dan sesuaikan setiap konversi dengan pengaturan yang memahami format.
Maks 2GB per file · Siap drag & drop · Berbagai jenis file diterima
SVGZ sekilas
SVGZ
SVG was developed by the W3C SVG Working Group starting in 1998, after six competing vector graphics submissions. SVG 1.0 became a W3C Recommendation on 4 September 2001, with SVGZ as the compressed variant.
SR2 sekilas
SR2
Early Sony raw formats reflect the transitional period in which Sony was still establishing its photography ecosystem and raw compatibility story.
Perbandingan format
| Fitur | SVGZ | SR2 |
|---|---|---|
| File type | Vector | Image |
| Extensions |
|
|
| MIME type |
|
|
| Created year | 2001 | 2003 |
| Inventor | World Wide Web Consortium (W3C) | Sony |
| Status | active | proprietary |
| Transparency | Tidak didukung | Tidak didukung |
| Animation | Tidak didukung | Tidak didukung |
| Primary use cases |
|
|
| Layer support | Tidak didukung | Tidak didukung |
| Vector scaling | Didukung | Tidak didukung |
Kapan memakai setiap format
When to use SVGZ
- Your source file is already in SVGZ.
- Preserve source expectations before exporting to SR2.
- SVGZ is commonly used in vector workflows.
When to use SR2
- Your target workflow expects SR2.
- Improve delivery compatibility with SR2.
- SR2 is commonly used in image workflows.
FAQ
Why convert SVGZ to SR2?
Convert to SR2 when maintaining an archive of older Sony raws or preserving compatibility with an earlier Sony camera workflow.
In most modern pipelines it is a source or recovery target rather than a preferred new output.
What changes when converting SVGZ to SR2?
This conversion changes how the format behaves in downstream tools and delivery environments.
Moving to SR2 removes vector scaling.
What should I review after converting SVGZ to SR2?
Validate output quality on representative files and confirm the target format behaves correctly in the destination workflow.