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
Convert to GBRUSH when the goal is to preserve or distribute a reusable bitmap brush for GIMP rather than export final artwork.
It is the right target for custom brush libraries, textured painting presets, and migration of legacy GIMP brush assets into a maintained toolkit.
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 | Krita Brush | 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 | 1996 | 2020 |
| Inventor | GIMP Development Team | 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 Krita Brush
- capture ingest
- editing
- web or print delivery
- Preserves reusable bitmap brush tips as authoring assets.
When to use NanoMD
- authoring
- review and collaboration
- distribution
- Keeps parsing and rendering requirements intentionally small.
FAQs
Why convert Krita Brush 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 Krita Brush to NanoMD?
This conversion changes how the format behaves in downstream tools and delivery environments.
Archival profile changes from moderate in Krita Brush to strong in NanoMD. Workflow profile changes from delivery in Krita Brush to exchange in NanoMD.
What should I review after converting Krita Brush 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..