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
MetaPost at a glance
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.
PGX at a glance
PGX
These formats persist in engineering, compression research, and conversion-tool contexts where simple sample storage or adjunct technical representation is useful.
Format comparison
| Feature | MetaPost | PGX |
|---|---|---|
| File type | Vector | Image |
| Extensions |
|
|
| MIME type |
|
|
| Created year | 1994 | 2000 |
| Inventor | John Hobby | ISO/IEC (JPEG 2000 committee) |
| Status | active | active |
| Transparency | Not supported | Not supported |
| Animation | Not supported | Not supported |
| Primary use cases |
|
|
| Layer support | Not supported | Not supported |
| Vector scaling | Supported | Not supported |
When to use each format
When to use MetaPost
- Your source file is already in MetaPost.
- Preserve source expectations before exporting to PGX.
- MetaPost is commonly used in vector workflows.
When to use PGX
- Your target workflow expects PGX.
- Improve delivery compatibility with PGX.
- PGX is commonly used in image workflows.
FAQs
Why convert MetaPost to PGX?
Convert to PGX when a technical imaging or codec workflow expects grayscale component data in a simple specialist format.
It is useful for research, testing, and standards-oriented image processing.
What changes when converting MetaPost to PGX?
This conversion changes how the format behaves in downstream tools and delivery environments.
Moving to PGX removes vector scaling.
What should I review after converting MetaPost to PGX?
Validate output quality on representative files and confirm the target format behaves correctly in the destination workflow.