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
KRA at a glance
KRA
Convert to KRA when the artwork needs to remain editable in Krita, especially for painting-heavy or layered illustration workflows.
It is the right target for preserving native editability during digital-art production.
RST at a glance
RST
Convert to RST when the content is headed into Sphinx or another documentation system that benefits from directive-rich plain text.
It is well suited to API docs, developer manuals, internal technical references, and documentation that needs cross-references, notes, code blocks, and publish-time transformations.
Use it when documentation semantics are more important than office-style page layout.
Format comparison
| Feature | KRA | RST |
|---|---|---|
| File type | Image | Document |
| Extensions |
|
|
| MIME type |
|
|
| Compression / quality | depends | depends |
| File size characteristics | medium | medium |
| Compatibility | broad | broad |
| Editability | moderate | moderate |
| Created year | 2005 | 2001 |
| Inventor | Krita / KDE community | Docutils project / David Goodger lineage |
| Status | proprietary | active |
| Primary use cases |
|
|
| Common software |
|
|
| Archival suitability | moderate | strong |
| Metadata handling | moderate | moderate |
| Delivery profile | strong | strong |
| Workflow fit | delivery | exchange |
| Vector scaling | ❌ | ❌ |
When to use each format
When to use KRA
- capture ingest
- editing
- web or print delivery
- Preserves editor-specific layered working state.
When to use RST
- authoring
- review and collaboration
- distribution
- Strong structural semantics for documentation.
FAQs
Why convert KRA to RST?
Convert to RST when the content is headed into Sphinx or another documentation system that benefits from directive-rich plain text.
It is well suited to API docs, developer manuals, internal technical references, and documentation that needs cross-references, notes, code blocks, and publish-time transformations.
Use it when documentation semantics are more important than office-style page layout.
What changes when converting KRA to RST?
This conversion changes how the format behaves in downstream tools and delivery environments.
Archival profile changes from moderate in KRA to strong in RST. Workflow profile changes from delivery in KRA to exchange in RST.
What should I review after converting KRA to RST?
Check the exported file for It has a steeper learning curve than Markdown for casual authors.; Outside technical-documentation communities, Markdown often wins on familiarity..