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
L16 at a glance
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.
NanoMD at a glance
NanoMD
Convert to NanoMD when the destination expects a restricted Markdown subset for internal docs, firmware-adjacent help files, or deliberately simple publishing workflows.
It is a good target when parser simplicity, deterministic formatting, or low-overhead tooling matters more than advanced authoring features.
Format comparison
| Feature | L16 | NanoMD |
|---|---|---|
| File type | Image | Document |
| Extensions |
|
|
| MIME type |
|
|
| Compression / quality | depends | depends |
| File size characteristics | medium | medium |
| Compatibility | broad | broad |
| Editability | moderate | moderate |
| Created year | 2016 | 2020 |
| Inventor | Light (formerly Lytro-era competitor) | Community (Markdown variant) |
| Status | active | active |
| Primary use cases |
|
|
| Common software |
|
|
| Archival suitability | moderate | strong |
| Metadata handling | moderate | moderate |
| Delivery profile | strong | strong |
| Workflow fit | delivery | exchange |
| Vector scaling | Not supported | Not supported |
When to use each format
When to use L16
- capture ingest
- editing
- web or print delivery
- Preserves exact 16-bit grayscale sample values.
When to use NanoMD
- authoring
- review and collaboration
- distribution
- Keeps parsing and rendering requirements intentionally small.
FAQs
Why convert L16 to NanoMD?
Convert to NanoMD when the destination expects a restricted Markdown subset for internal docs, firmware-adjacent help files, or deliberately simple publishing workflows.
It is a good target when parser simplicity, deterministic formatting, or low-overhead tooling matters more than advanced authoring features.
What changes when converting L16 to NanoMD?
This conversion changes how the format behaves in downstream tools and delivery environments.
Archival profile changes from moderate in L16 to strong in NanoMD. Workflow profile changes from delivery in L16 to exchange in NanoMD.
What should I review after converting L16 to NanoMD?
Check the exported file for Public documentation and ecosystem visibility are limited compared with mainstream markup formats.; Compatibility with broader Markdown tooling cannot be assumed..