Image MIME Reference
EDMICS-RLC
Fuji Xerox EDMICS-RLC
image/vnd.fujixerox.edmics-rlc
VS
Tencent TAP Image
image/vnd.tencent.tap
Tencent-TAP
A complete technical comparison of Fuji Xerox EDMICS-RLC and Tencent TAP Image — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.
Equal browser support
Feature Support
| Feature | EDMICS-RLC | Tencent-TAP |
|---|---|---|
| Transparency (Alpha) | ✕ No | ✕ No |
| Animation Support | ✕ No | ✕ No |
| Progressive Loading | ✕ No | ✕ No |
| HDR Support | ✕ No | ✕ No |
| EXIF Metadata | ✕ No | ✕ No |
| ICC Color Profile | ✕ No | ✕ No |
Fuji Xerox EDMICS-RLC
image/vnd.fujixerox.edmics-rlc
Extension
.rlc.edm
Container
Fuji Xerox EDMICS Wrapper
Compression
Run-Length Coding (RLC / RLE)
Algorithm
Run-Length Coding (RLC)
Color Depth
1-bit (Monochrome), 8-bit (Grayscale)
Developed by
Fuji Xerox Co., Ltd.
Released
1990s
Magic Bytes
Unknown (Proprietary Container)
Tencent TAP Image
image/vnd.tencent.tap
Extension
.tap
Container
Proprietary Tencent Container
Compression
Unknown (Proprietary)
Algorithm
Unknown
Color Depth
Unknown
Developed by
Tencent (Registered by Ni Hui)
Released
2014
Magic Bytes
Unknown (Proprietary)
Browser Support Comparison
| Browser | EDMICS-RLC | Tencent-TAP |
|---|---|---|
|
|
✕ | ✕ |
|
|
✕ | ✕ |
|
|
✕ | ✕ |
|
|
✕ | ✕ |
|
|
✕ | ✕ |
EDMICS-RLC
EDMICS-RLC Strengths
- Simple, computationally inexpensive Run-Length Coding enabled rapid compression and decompression on low-power legacy hardware
- Deeply integrated into Fuji Xerox enterprise hardware for seamless, automated scan-to-archive workflows
Limitations
- Completely proprietary and closed-source, making modern archival extraction and migration extremely difficult
- No support in modern image processing libraries like ImageMagick, libvips, or standard viewers without bespoke decoding tools
- RLC compression is far less efficient than modern algorithms like PNG (Deflate) for complex documents
Tencent-TAP
Tencent-TAP Strengths
- Officially registered with IANA, ensuring a unique MIME type identifier for internal Tencent network routing and content negotiation
Limitations
- Completely undocumented and closed-source, making it impossible to decode or parse outside of Tencent's software
- Shares its file extension (.tap) with numerous other established legacy formats, leading to frequent automated file misidentification by Node/Python libraries
When to choose which format
EDMICS-RLC
Use EDMICS-RLC when…
- Fuji Xerox EDMICS Enterprise Systems
- Archival of Scanned Engineering Documents
- Legacy Corporate Scanning Pipelines
Tencent-TAP
Use Tencent-TAP when…
- Internal Tencent Ecosystem Applications
- Proprietary Mobile or Gaming Assets