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
GeoJSON at a glance
GeoJSON
—
TOML at a glance
TOML
—
Format comparison
| Feature | GeoJSON | TOML |
|---|---|---|
| File type | Other | Other |
| Status | active | active |
| Transparency | Not supported | Not supported |
| Animation | Not supported | Not supported |
| Primary use cases |
|
|
| Vector scaling | Supported | Not supported |
| Reflowable text | Not supported | Not supported |
| Structured data | Supported | Supported |
| Streaming ready | Not supported | Not supported |
When to use each format
When to use GeoJSON
- Your source file is already in GeoJSON.
- Preserve source expectations before exporting to TOML.
- GeoJSON is commonly used in other workflows.
When to use TOML
- Your target workflow expects TOML.
- Improve delivery compatibility with TOML.
- TOML is commonly used in other workflows.
FAQs
Why convert GeoJSON to TOML?
This conversion is usually chosen when TOML fits downstream other delivery better.
What changes when converting GeoJSON to TOML?
This conversion changes how the format behaves in downstream tools and delivery environments.
Moving to TOML removes vector scaling.
What should I review after converting GeoJSON to TOML?
Validate output quality on representative files and confirm the target format behaves correctly in the destination workflow.