Convert WMF to QOI

Drag and drop files here or click to select.
Max file size 100mb.
Uploading progress:

WMF vs QOI Format Comparison

Aspect WMF (Source Format) QOI (Target Format)
Format Overview
WMF
Windows Metafile

A 16-bit vector/raster graphics format introduced with Windows 3.0 in 1990. WMF stores GDI (Graphics Device Interface) drawing commands including lines, shapes, text, and embedded bitmaps. It was widely used for clip art in Microsoft Office and corporate document templates throughout the 1990s and 2000s. As a legacy format, it has significant security concerns and no modern browser support.

Legacy Format Lossless
QOI
Quite OK Image Format (QOI)

QOI (Quite OK Image Format) was created by Dominic Szablewski in 2021. It is designed to be the simplest possible lossless image format with good compression and extremely fast encoding/decoding.

Modern Format Lossless
Technical Specifications
Type: 16-bit vector/raster metafile
Drawing Model: Windows GDI commands
Transparency: Not supported
Animation: Not supported
Extensions: .wmf
Color Depth: 24-bit RGB or 32-bit RGBA
Compression: Custom lossless (run, index, diff, luma)
Transparency: Full 8-bit alpha channel (RGBA mode)
Animation: Not supported
Extensions: .qoi
Image Features
  • Vector Graphics: Stores GDI drawing commands, not pixels
  • Raster Support: Can embed bitmap images within vector container
  • Text Rendering: Windows font rendering via GDI text commands
  • Color Model: Windows GDI RGB color space
  • Scalability: Resolution-independent vector content
  • Metadata: Minimal header with bounding box and DPI info
  • Transparency: Full 8-bit alpha channel in RGBA mode
  • Compression: Ultra-fast lossless with 4 simple operations
  • Speed: 20-50x faster encoding than PNG
  • Simplicity: ~300 lines of code for full implementation
  • Streaming: Single-pass encoding and decoding
  • Deterministic: Same input always produces same output
Processing & Tools

WMF rendering requires Windows GDI or compatible libraries:

# Convert WMF using ImageMagick
magick input.wmf output.png

# Convert WMF using LibreOffice
libreoffice --headless \
  --convert-to png input.wmf

# Python with Pillow
from PIL import Image
img = Image.open("input.wmf")

QOI creation and processing tools:

# Convert to QOI using ImageMagick
magick input.wmf output.qoi

# Python with Pillow
from PIL import Image
img = Image.open("input.wmf")
img.save("output.qoi")

# Batch convert directory
magick mogrify -format qoi \
  *.wmf
Advantages
  • Resolution-independent vector graphics scale to any size
  • Compact file size for complex drawings (stores commands, not pixels)
  • Native support in all Microsoft Office applications
  • Supports text, shapes, lines, and embedded bitmaps
  • Widely used in legacy corporate document templates
  • Can be rendered at any DPI without quality loss
  • Extremely fast encoding (20-50x faster than PNG)
  • Simple specification (~300 lines reference implementation)
  • Lossless compression with competitive ratios
  • Full alpha transparency support
  • Deterministic output for reproducible builds
  • Public domain / MIT licensed, zero patent concerns
Disadvantages
  • 16-bit format with limited GDI command set
  • No support in web browsers or modern viewers
  • Security vulnerabilities in WMF parsing (historical exploits)
  • No transparency or alpha channel support
  • Windows-only format, poor cross-platform support
  • Larger files than optimized PNG for most images
  • Very limited software support compared to PNG
  • No progressive loading or interlacing
  • No metadata support (EXIF, ICC profiles)
  • Not supported by web browsers
Common Uses
  • Legacy Microsoft Office clip art libraries
  • Embedded graphics in Word and PowerPoint documents
  • Corporate document templates and letterheads
  • Windows application resource graphics
  • Early desktop publishing clip art collections
  • Game engine texture caching (fast load times)
  • Real-time image processing intermediate format
  • Embedded systems requiring fast lossless images
  • Screenshot capture with minimal encoding latency
  • Development and prototyping image pipelines
Best For
  • Legacy Microsoft Office document graphics
  • Scalable clip art in Windows environments
  • Corporate templates from the Windows 3.x/95/XP era
  • Vector graphics within the Microsoft GDI ecosystem
  • Applications where encoding speed is critical
  • Game engines needing fast texture loading
  • Real-time systems with lossless image requirements
  • Embedded platforms with limited CPU power
Version History
Introduced: 1990 (Microsoft, Windows 3.0)
Current Version: WMF (16-bit), EMF (32-bit successor)
Status: Legacy, superseded by EMF/EMF+
Evolution: WMF (1990) → EMF (1993) → EMF+ (2000, GDI+)
Introduced: 2021 (Dominic Szablewski)
Current Version: QOI 1.0 (2022, stable specification)
Status: Growing adoption, spec frozen at 1.0
Evolution: Initial release (2021) → QOI 1.0 spec (2022)
Software Support
Office Apps: Word, PowerPoint, Publisher (legacy versions)
Web Browsers: Not supported in any browser
OS Preview: Windows (native GDI), limited macOS/Linux
Image Editors: LibreOffice Draw, Inkscape (import), GIMP (limited)
CLI Tools: ImageMagick, LibreOffice CLI, Pillow
Image Editors: GIMP (via plugin), limited editor support
Web Browsers: Not supported in web browsers
OS Preview: Via libraries (qoi.h reference implementation)
Mobile: Via third-party libraries
CLI Tools: qoiconv (reference), Pillow 12+, ImageMagick 7.1+

Why Convert WMF to QOI?

Converting WMF to QOI leverages the fastest lossless image encoding available, making it ideal for batch converting large WMF clip art libraries where encoding speed matters more than maximum compression. QOI encodes 20-50 times faster than PNG while achieving competitive file sizes, significantly reducing processing time for large-scale conversion jobs.

Game developers and real-time applications benefit from QOI's ultra-fast decoding when loading converted WMF graphics as runtime assets. Where PNG decompression might cause frame drops, QOI loads almost instantly with minimal CPU overhead, making it suitable for texture caching systems and real-time UI rendering.

For development and prototyping workflows, QOI's simplicity (the entire format specification fits in 300 lines of code) makes it easy to integrate into custom tools and pipelines. Converting WMF graphics to QOI creates a fast-loading intermediate format that developers can read, process, and write with minimal library dependencies.

Note that QOI has limited software support compared to PNG and is not displayable in web browsers. While QOI files are slightly larger than optimized PNG for most images, the dramatic speed advantage makes it worthwhile for performance-sensitive applications. For web or general distribution, PNG or WebP remain the standard choices.

Key Benefits of Converting WMF to QOI:

  • Ultra-Fast Encoding: 20-50x faster than PNG, ideal for batch conversion
  • Lossless Quality: Perfect pixel reproduction with no compression artifacts
  • Alpha Transparency: Full 8-bit alpha channel support for clip art overlays
  • Simple Format: 300-line specification, trivial to implement in any language
  • Fast Decoding: Near-instant image loading for real-time applications
  • Patent Free: Public domain specification with no licensing concerns
  • Deterministic: Reproducible output for automated build pipelines

Practical Examples

Example 1: Game Engine Texture Cache

Scenario: A game developer converts WMF UI assets to QOI for a fast-loading texture cache system in a 2D game engine.

Source: ui_elements.wmf (10 KB)
Rasterize at 512x512px
Convert WMF → QOI RGBA
Result: ui_elements.qoi (85 KB)

- RGBA with alpha transparency
- Decodes in <1ms on modern CPU
- 20x faster than PNG loading
- No codec library dependency

Example 2: Batch Clip Art Conversion Pipeline

Scenario: An IT department batch converts 10,000 WMF clip art files using QOI as the intermediate format before final PNG optimization.

Source: 10,000 WMF files (avg 12 KB)
Rasterize at 1024x1024px each
Convert WMF → QOI (batch)
Result: 10,000 QOI files

Batch timing:
- QOI: 10,000 files in 45 seconds
- PNG: 10,000 files in 15 minutes
- 20x faster batch processing
- Intermediate before PNG optimization

Example 3: Embedded System Display Assets

Scenario: An embedded developer converts WMF graphics to QOI for a kiosk display system with limited CPU for image decoding.

Source: menu_screen.wmf (18 KB)
Rasterize at 800x600px
Convert WMF → QOI RGB
Result: menu_screen.qoi (120 KB)

- Decodes on low-power ARM SoC
- No zlib dependency needed
- Single-pass stream decoding
- Minimal memory footprint

Frequently Asked Questions (FAQ)

Q: What is QOI and who created it?

A: QOI (Quite OK Image Format) was created by Dominic Szablewski in 2021. It is designed to be the simplest possible lossless image format with good compression and extremely fast encoding/decoding. The entire specification is about 300 lines of C code.

Q: How does QOI compare to PNG?

A: QOI encodes 20-50x faster and decodes 3-4x faster than PNG. However, QOI files are typically 10-30% larger than optimized PNG. QOI trades some compression efficiency for dramatic speed improvements. For web delivery, PNG is still preferred for its smaller size and universal support.

Q: Can web browsers display QOI images?

A: No. QOI is not supported by any web browser. For web use, convert to PNG, WebP, or AVIF. QOI is designed for applications where encoding/decoding speed is more important than broad compatibility.

Q: Is QOI suitable for archival storage?

A: QOI is lossless and deterministic, so the quality is archival-grade. However, the format is very new (2021) and has limited software support. For long-term archival, PNG or TIFF are safer choices due to their decades of universal support.

Q: Does QOI support metadata?

A: No. QOI has no support for EXIF, ICC profiles, or any metadata beyond image dimensions and color space. This is by design — the format prioritizes simplicity and speed over features.

Q: What color modes does QOI support?

A: QOI supports two modes: RGB (3 bytes per pixel) and RGBA (4 bytes per pixel with alpha). There is no grayscale, palette, or 16-bit mode. The format is designed for standard 8-bit-per-channel images.

Q: How large are QOI files?

A: QOI files are typically similar in size to non-optimized PNG files. For a 1024x1024 clip art image, expect 50-200 KB depending on complexity. Simple flat-color WMF art compresses very well in QOI due to its run-length and difference encoding.

Q: Can QOI replace PNG?

A: Not for general use. QOI lacks PNG's metadata support, progressive loading, and universal software/browser support. QOI is complementary — use it where speed matters (game engines, real-time systems, batch processing) and PNG where compatibility and features matter (web, documents, sharing).