ANE-LX3
What this fingerprint profile shows
Every photo taken by a ANE-LX3 carries a consistent set of metadata patterns — written automatically by the firmware at the moment of capture, regardless of any app or privacy setting. The signals below are derived from 17 analysed files and document exactly what this device embeds in every image it creates.
GPS rate — how often this device records your precise location in the file, even when you don't realise GPS is active
DQT compression fingerprint — a unique 64-value matrix baked into the firmware that identifies this camera model even after EXIF metadata has been stripped
MakerNote & firmware strings — proprietary manufacturer data and firmware version tags that reveal processing history, lens details, and scene settings
Privacy risk signals — owner name, body serial number, and lens serial number fields that may contain personally identifying information
Further reading — snapWONDERS Founder:
All patterns are aggregated and anonymous — no originals retained. Privacy details →
Your ANE-LX3 embeds these signals in every photo you share.
Strip with VaultifyOutput DimensionsImage resolution values (width × height in pixels) observed across analysed files from this device.
Image resolution values observed for this device.
| Observed value | |
|---|---|
| 1080x2280 |
SOF Compression TypeStart of Frame marker — identifies the JPEG compression algorithm. SOF0 = baseline DCT (most common); SOF2 = progressive DCT (multiple passes, common in web-optimised images).
JPEG compression markers (SOF0 = baseline, SOF2 = progressive).
| Observed value | |
|---|---|
| SOF0 |
DQT Quantisation Table FingerprintsThe 64-value matrix that controls JPEG lossy compression. Baked into firmware — consistent across units of the same model — and distinctive enough to act as a camera fingerprint.
JPEG quantisation table fingerprints. Identical patterns across devices indicate shared hardware or firmware lineage.
1
distinct fingerprint accumulated
JPEG Segment InventoryThe set of JPEG markers consistently present in output from this device. Marker presence and order are firmware-determined and can help distinguish camera lineages.
APP and SOF segments consistently present in output from this device.
| Observed value | |
|---|---|
| APP1Primary metadata container — holds EXIF camera data (make, model, GPS, settings) and optionally XMP. | |
| APP0JFIF application marker — identifies the file as JFIF format and may carry thumbnail and pixel density info. | |
| DHTDefine Huffman Table — the compression lookup table baked in by the encoder. | |
| DQTDefine Quantization Table — the 64-value lossy compression matrix. Consistent per firmware; useful as a fingerprint. | |
| SOF0Start of Frame, Baseline DCT — the most common JPEG compression type. | |
| SOSStart of Scan — marks the beginning of the compressed image data stream. | |
| SOIStart of Image — the 2-byte marker that opens every valid JPEG file. | |
| EOIEnd of Image — the 2-byte marker that closes every valid JPEG file. |
Metadata Block TypesThe metadata container formats found in files from this device — EXIF, IPTC, XMP, JFIF, and others. Different devices and software pipelines embed different combinations.
| Observed value | |
|---|---|
| Exif | |
| JFIFJPEG File Interchange Format — a baseline format header. Often absent from camera-original files; common in scanned or web-converted images. |
Your photos carry this device fingerprint.
Vaultify strips device metadata before sharing — and can hide a private message inside your photo, invisible to forensic scanners like these.
