Converteer alles, op wereldwijde schaal.
Meer dan 200 formaten en automatiserings-API's die direct aanvoelen.
CONVERT
Van
Naar
Sleep bestanden hierheen of kies een bron
Upload meerdere bestanden tegelijk, combineer formaten en stel elke conversie nauwkeurig af met formaatbewuste instellingen.
Maximaal 2 GB per bestand · Klaar voor slepen en neerzetten · Gemengde bestandstypen welkom
MetaPost in het kort
MetaPost
John Hobby developed MetaPost from MetaFont ideas, and the system later evolved into the MPlib era so TeX and LuaTeX workflows could keep high-quality vector graphics close to typeset documents.
XCF in het kort
XCF
XCF reflects the long history of GIMP as an open-source raster editor with its own native document model rather than as a lightweight clone of consumer image viewers.
Formaatvergelijking
| Kenmerk | MetaPost | XCF |
|---|---|---|
| File type | Vector | Image |
| Extensions |
|
|
| MIME type |
|
|
| Created year | 1994 | 1995 |
| Inventor | John Hobby | GIMP community |
| Status | active | proprietary |
| Transparency | Niet ondersteund | Niet ondersteund |
| Animation | Niet ondersteund | Niet ondersteund |
| Primary use cases |
|
|
| Layer support | Niet ondersteund | Ondersteund |
| Vector scaling | Ondersteund | Ondersteund |
Wanneer je elk formaat gebruikt
When to use MetaPost
- Your source file is already in MetaPost.
- Preserve source expectations before exporting to XCF.
- MetaPost is commonly used in vector workflows.
When to use XCF
- Your target workflow expects XCF.
- Improve delivery compatibility with XCF.
- XCF is commonly used in image workflows.
Veelgestelde vragen
Why convert MetaPost to XCF?
Convert to XCF when artwork needs to remain editable in GIMP, especially for layered image editing, compositing, and open-source creative workflows.
It is the right target for preserving GIMP-native editability.
What changes when converting MetaPost to XCF?
This conversion changes how the format behaves in downstream tools and delivery environments.
Moving to XCF adds layer support.
What should I review after converting MetaPost to XCF?
Validate output quality on representative files and confirm the target format behaves correctly in the destination workflow.