Convert FLI to QOI
Max file size 100mb.
FLI vs QOI Format Comparison
| Aspect | FLI (Source Format) | QOI (Target Format) |
|---|---|---|
| Format Overview |
FLI
Autodesk FLIC Animation
Animation format created by Autodesk in 1985 for Animator and Animator Pro. Stores frame-by-frame animation with 256-color palette and delta compression. FLI uses fixed 320x200 resolution while FLC supports arbitrary sizes. Ubiquitous in DOS-era games and multimedia. Legacy Format Lossless |
QOI
Quite OK Image Format
Minimalist lossless image format created by Dominic Szablewski in 2021. Designed for simplicity with a specification that fits on a single page. Achieves compression comparable to PNG but with 20-50x faster encoding and 3-4x faster decoding. Gaining rapid adoption for real-time applications. Modern Format Lossless |
| Technical Specifications |
Structure: Chunk-based binary with frame delta compression
Color Depth: 8-bit indexed (256-color palette) Resolution: FLI: 320×200 fixed, FLC: arbitrary Compression: RLE + delta frame encoding Extensions: .fli, .flc |
Structure: 14-byte header + ops stream + 8-byte end
Color Depth: 24-bit RGB or 32-bit RGBA Compression: Run-length + index + delta + full pixel Transparency: Full alpha channel (32-bit) Extensions: .qoi |
| Syntax Examples |
FLI uses binary format (not human-readable): Header: 128 bytes Magic: 0xAF11 (FLI) / 0xAF12 (FLC) Frames: N, Width: W, Height: H Depth: 8 bits, Delay: D ms Frame chunks: delta-compressed |
QOI uses a minimal binary format: Header: 14 bytes Magic: "qoif" Width, Height (32-bit BE) Channels: 3 (RGB) or 4 (RGBA) Colorspace: 0=sRGB, 1=linear Ops: index/diff/luma/run/rgb/rgba End: 8 bytes (0x00...0x01) |
| Content Support |
|
|
| Advantages |
|
|
| Disadvantages |
|
|
| Common Uses |
|
|
| Best For |
|
|
| Version History |
FLI Introduced: 1985 (Autodesk Animator)
FLC Introduced: 1992 (Animator Pro) Status: Legacy (no longer developed) Evolution: Superseded by AVI, MPEG, MP4 |
Introduced: 2021 (Dominic Szablewski)
Version: QOI 1.0 (specification final) Status: Active, growing adoption Evolution: New format, no predecessors |
| Software Support |
Pillow (Python): Native read support (FliImagePlugin)
FFmpeg: Full read/write support ImageMagick: Read support Other: XnView, IrfanView, GIMP (via plugin) |
Pillow: Native support (12.0+)
Libraries: qoi-ci (C), qoi-rust, qoijs Tools: ImageMagick 7.1+, XnView Other: Godot Engine, FFmpeg (recent) |
Why Convert FLI to QOI?
Converting FLI animation frames to QOI provides ultra-fast lossless encoding that's ideal for real-time applications and game development. QOI encodes 20-50x faster than PNG while achieving comparable file sizes, making it perfect for rapid batch conversion of animation frame sequences.
QOI's simple format specification and fast decode speed make it excellent for game engines and real-time applications. If you're extracting FLI animation frames for use in a game or interactive application, QOI provides the fastest possible lossless image loading.
The format's color index and run-length encoding are particularly effective for palette-based content like FLI frames, where repeated colors and pixel patterns are common. QOI achieves excellent compression ratios on this type of content.
QOI is gaining rapid adoption in the game development and real-time graphics communities. As a modern format designed for speed, it represents the cutting edge of lossless image compression with a growing ecosystem of tools and libraries.
Key Benefits of Converting FLI to QOI:
- Ultra-Fast Encoding: QOI encodes 20-50x faster than PNG — ideal for batch conversion
- Fast Decoding: QOI decodes 3-4x faster than PNG for real-time applications
- Lossless Quality: Zero quality loss with competitive compression ratios
- Alpha Support: Full 32-bit RGBA for transparency and compositing
- Simple Format: One-page specification — easy to implement and debug
- Game Dev Ready: Adopted by Godot Engine and growing game development ecosystem
- Pillow Native: Both FLI and QOI supported by Python Pillow 12+
Practical Examples
Example 1: Real-Time Frame Buffer
Input FLI file (game.fli):
FLI animation file: Resolution: 320x200 Colors: 256-color palette Content: Game animation Real-time extraction
Output QOI file (frame.qoi):
QOI lossless output: ✓ Ultra-fast encoding ✓ Lossless quality ✓ File size: ~15-30 KB ✓ 20x faster than PNG encode ✓ 3x faster decode ✓ Game engine compatible ✓ Minimal CPU overhead
Example 2: Batch Animation Export
Input FLI file (animation.flc):
FLC animation file: Resolution: 640x480 Colors: 256 indexed Frames: 500 Batch export needed
Output QOI file (batch_frame.qoi):
QOI batch output: ✓ Near-instant encoding ✓ 500 frames in seconds ✓ Lossless preservation ✓ Competitive file sizes ✓ No encoding bottleneck ✓ Pipeline-friendly ✓ Minimal resource usage
Example 3: Embedded System Graphics
Input FLI file (ui.fli):
FLI UI animation: Resolution: 320x200 Colors: 256 palette Content: Embedded UI Resource-constrained target
Output QOI file (embedded.qoi):
Embedded QOI: ✓ Tiny decoder footprint ✓ No complex dependencies ✓ Fast decode on weak CPU ✓ Lossless graphics ✓ Simple implementation ✓ Memory efficient ✓ Embedded systems ready
Frequently Asked Questions (FAQ)
Q: What is QOI format?
A: QOI (Quite OK Image) is a lossless image format created by Dominic Szablewski in 2021. Its specification fits on a single page, yet it achieves compression comparable to PNG with 20-50x faster encoding and 3-4x faster decoding. It supports RGB and RGBA images.
Q: Why choose QOI over PNG?
A: Choose QOI when speed is more important than file size. QOI encodes dramatically faster than PNG with slightly larger files (10-20% larger on average). For real-time applications, game engines, batch processing, and embedded systems, QOI's speed advantage is significant.
Q: Can browsers display QOI?
A: No, QOI is not supported by web browsers. For web display, use PNG, WebP, or AVIF. QOI is designed for application-level use where custom loaders are available, not for web content delivery.
Q: How does QOI compression work?
A: QOI uses four simple operations: an index of 64 recently-seen colors, small differences from the previous pixel, luma-weighted deltas, and run-length encoding for repeated pixels. Full RGB(A) values are stored only when no shortcut applies. This simplicity enables very fast encoding.
Q: Is QOI good for pixel art?
A: Excellent. QOI's color index and run-length encoding handle pixel art's flat colors and repeated patterns very efficiently. FLI's palette-based pixel art is an ideal use case for QOI compression, often achieving better ratios than on photographic content.
Q: Does QOI support animation?
A: No, QOI is a single-frame format. For animated output from FLI, consider GIF, animated WebP, or APNG. QOI is designed for individual images where encoding and decoding speed are priorities.
Q: What software supports QOI?
A: QOI is supported by Pillow 12+, ImageMagick 7.1+, XnView, Godot Engine, and many game development tools. Libraries exist for C, Rust, JavaScript, Go, and most programming languages. The ecosystem is growing rapidly since the format's 2021 release.
Q: Is QOI an open format?
A: Yes, QOI is fully open source with a permissive MIT license. The specification, reference implementation, and test suite are all freely available. There are no patents or licensing requirements for implementing QOI encoders or decoders.