Corel Binary metafile (.clb)
.clb file signature | application/octet-stream
Corel Binary metafile
Magic Bytes
Offset 0
43 4D 58 31
Sources: Gary Kessler
All Known Signatures
2 signature variants are documented for .clb files across multiple sources.
| Hex Signature | Offset | Sources |
|---|---|---|
| 43 4D 58 31 | 0 | Gary Kessler |
| 43 4F 4D 2B | 0 | Gary Kessler |
Extension
.clb
MIME Type
application/octet-stream
Byte Offset
0
Risk Level
Safe
Validation Code
How to validate .clb files in Python
def is_clb(file_path: str) -> bool:
"""Check if file is a valid CLB by magic bytes."""
signature = bytes([0x43, 0x4D, 0x58, 0x31])
with open(file_path, "rb") as f:
return f.read(4) == signatureHow to validate .clb files in Node.js
function isCLB(buffer: Buffer): boolean {
const signature = Buffer.from([0x43, 0x4D, 0x58, 0x31]);
return buffer.subarray(0, 4).equals(signature);
}How to validate .clb files in Go
func IsCLB(data []byte) bool {
signature := []byte{0x43, 0x4D, 0x58, 0x31}
if len(data) < 4 {
return false
}
return bytes.Equal(data[:4], signature)
}API Endpoint
/api/v1/clb
curl https://filesignature.org/api/v1/clb
See the full API documentation for all endpoints and parameters.
Frequently Asked Questions
What is a .clb file?
A .clb file is a Corel Binary metafile file. Corel Binary metafile
What are the magic bytes for .clb files?
The magic bytes for Corel Binary metafile files are 43 4D 58 31 at byte offset 0. These bytes uniquely identify the file format regardless of the file extension.
How do I validate a .clb file?
To validate a .clb file, read the first bytes of the file and compare them against the known magic bytes (43 4D 58 31) at offset 0. This is more reliable than checking the file extension alone, as extensions can be renamed.
What is the MIME type for .clb files?
There is no officially registered MIME type for .clb files. Systems typically use application/octet-stream as a generic fallback when handling this format.
Is it safe to open .clb files?
Corel Binary metafile (.clb) files are generally safe to open. They are classified as low risk because they primarily contain data rather than executable code. However, always ensure files come from a trusted source.