Convert anything, at global scale.
200+ formats and automation APIs that feels instant.
CONVERT
From
To
Drop files or choose a source
Upload multiple files at once, mix formats, and fine-tune every conversion with format-aware settings.
Max 2GB per file · Drag & drop ready · Mixed file types welcome
SRF at a glance
SRF
Convert to SRF when preserving older Sony originals or keeping a legacy Sony raw library intact.
It is useful for archive recovery and compatibility workflows.
SVGZ at a glance
SVGZ
Convert to SVGZ when you need SVG semantics but want the file itself stored or transmitted in compressed form.
It is most useful for web asset pipelines, map layers, and technical graphics repositories where vector fidelity matters and pre-compressed files are already part of the deployment model.
If the downstream environment already applies gzip or brotli to ordinary SVG responses, plain SVG is often easier to work with.
Choose SVGZ when the consumer explicitly expects it or when archived asset size is worth prioritizing.
Format comparison
| Feature | SRF | SVGZ |
|---|---|---|
| File type | Image | Vector |
| Extensions |
|
|
| MIME type |
|
|
| Compression / quality | raw | scalable |
| File size characteristics | large | small |
| Compatibility | limited | moderate |
| Editability | high | high |
| Created year | 2003 | 2001 |
| Inventor | Sony | World Wide Web Consortium (W3C) |
| Status | proprietary | active |
| Transparency | Not supported | Not supported |
| Animation | Not supported | Not supported |
| Primary use cases |
|
|
| Common software |
|
|
| Archival suitability | strong | good |
| Metadata handling | rich | moderate |
| Delivery profile | limited | strong |
| Workflow fit | source | design |
| Layer support | Not supported | Not supported |
| Vector scaling | Not supported | Supported |
When to use each format
When to use SRF
- capture ingest
- editing
- web or print delivery
- Preserve capture-stage sensor information.
When to use SVGZ
- illustration
- diagramming
- brand asset delivery
- Significantly smaller than uncompressed SVG.
FAQs
Why convert SRF to SVGZ?
Convert to SVGZ when you need SVG semantics but want the file itself stored or transmitted in compressed form.
It is most useful for web asset pipelines, map layers, and technical graphics repositories where vector fidelity matters and pre-compressed files are already part of the deployment model.
If the downstream environment already applies gzip or brotli to ordinary SVG responses, plain SVG is often easier to work with.
Choose SVGZ when the consumer explicitly expects it or when archived asset size is worth prioritizing.
What changes when converting SRF to SVGZ?
This conversion changes how the format behaves in downstream tools and delivery environments.
Size profile changes from large in SRF to small in SVGZ. Quality profile changes from raw in SRF to scalable in SVGZ. Compatibility profile changes from limited in SRF to moderate in SVGZ. Archival profile changes from strong in SRF to good in SVGZ. Metadata profile changes from rich in SRF to moderate in SVGZ. Delivery profile changes from limited in SRF to strong in SVGZ. Workflow profile changes from source in SRF to design in SVGZ.
Moving to SVGZ adds vector scaling.
What should I review after converting SRF to SVGZ?
Check the exported file for Not human-readable without decompression.; Requires correct HTTP headers for web delivery.; Cannot be edited directly — must decompress first..