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