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
Krita Brush at a glance
Krita Brush
—
MetaPost at a glance
MetaPost
—
Format comparison
| Feature | Krita Brush | MetaPost |
|---|---|---|
| File type | Image | Vector |
| Status | active | active |
| Transparency | Not supported | Not supported |
| Animation | Not supported | Not supported |
| Primary use cases |
|
|
| Layer support | Supported | Not supported |
| Vector scaling | Not supported | Supported |
When to use each format
When to use Krita Brush
- Your source file is already in Krita Brush.
- Preserve source expectations before exporting to MetaPost.
- Krita Brush is commonly used in image 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 Krita Brush to MetaPost?
This conversion is usually chosen when MetaPost fits downstream vector delivery better.
What changes when converting Krita Brush to MetaPost?
This conversion changes how the format behaves in downstream tools and delivery environments.
Moving to MetaPost removes layer support. Moving to MetaPost adds vector scaling.
What should I review after converting Krita Brush to MetaPost?
Validate output quality on representative files and confirm the target format behaves correctly in the destination workflow.