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
FITS at a glance
FITS
FITS became a durable scientific standard because observatories, spacecraft, and analysis tools needed a stable interchange format that outlived individual instruments and software stacks.
L16 at a glance
L16
The slug appears in product data with Light-camera lineage, but public documentation is sparse enough that the safer interpretation is a specialist raw grayscale interchange usage rather than a fully published neutral format family.
Format comparison
| Feature | FITS | L16 |
|---|---|---|
| File type | Image | Image |
| Extensions |
|
|
| MIME type |
|
|
| Created year | 1981 | 2016 |
| Inventor | NASA / astronomical data community | Light (formerly Lytro-era competitor) |
| Status | active | active |
| Transparency | Not supported | Not supported |
| Animation | Not supported | Not supported |
| Primary use cases |
|
|
| Layer support | Not supported | Not supported |
| Vector scaling | Not supported | Not supported |
| Camera raw data | Not supported | Not supported |
| HDR support | Not supported | Not supported |
| Streaming ready | Not supported | Not supported |
When to use each format
When to use FITS
- Your source file is already in FITS.
- Preserve source expectations before exporting to L16.
- FITS is commonly used in image workflows.
When to use L16
- Your target workflow expects L16.
- Improve delivery compatibility with L16.
- L16 is commonly used in image workflows.
FAQs
Why convert FITS to L16?
Scientific and medical raw image data where each pixel's exact 16-bit value must be preserved: fluorescence microscopy, remote sensing, and instrument image pipelines.
What changes when converting FITS to L16?
This conversion changes how the format behaves in downstream tools and delivery environments.
What should I review after converting FITS to L16?
Validate output quality on representative files and confirm the target format behaves correctly in the destination workflow.