vivo 1601
All patterns are aggregated and anonymous — no originals retained. Privacy details →
GPS Metadata RateThe proportion of files where this device embedded GPS coordinates — from an on-board receiver or a paired smartphone.
Percentage of files from this device that contained GPS location data.
Output DimensionsImage resolution values (width × height in pixels) observed across analysed files from this device.
Image resolution values observed for this device.
| Observed value | |
|---|---|
| 2136x2284 | |
| 2352x4160 |
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 | |
|---|---|
| DHTDefine Huffman Table — the compression lookup table baked in by the encoder. | |
| SOF0Start of Frame, Baseline DCT — the most common JPEG compression type. | |
| SOSStart of Scan — marks the beginning of the compressed image data stream. | |
| APP1Primary metadata container — holds EXIF camera data (make, model, GPS, settings) and optionally XMP. | |
| DQTDefine Quantization Table — the 64-value lossy compression matrix. Consistent per firmware; useful as a fingerprint. | |
| APP0JFIF application marker — identifies the file as JFIF format and may carry thumbnail and pixel density info. | |
| 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. | |
| APP6 | |
| APP8 | |
| APP7 | |
| APP5 |
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. | |
| XMPExtensible Metadata Platform — Adobe's XML-based metadata layer for editing history, rights, and additional descriptive data. | |
| XAPEarly Adobe XMP namespace prefix (xap:) used before xmp: was standardised. Seen in older cameras and Photoshop CS versions. |
EXIF VersionThe EXIF specification version string written by the device's firmware. Not user-adjustable — a firmware constant that can indicate manufacturing era.
EXIF specification version string encoded by this device's firmware. Not user-adjustable — firmware constant.
| Observed value | |
|---|---|
| 0220 |
Software / Firmware StringsValues written to the EXIF Software tag — may reflect firmware version, in-camera processing software, or the desktop application used to export the file.
Values written to the EXIF Software tag by this device or its associated software.
| Observed value | |
|---|---|
| MediaTek Camera Application |
Y/CbCr PositioningSpecifies how chroma channels (Cb, Cr) align with the luma channel (Y) during colour subsampling. Centred (1) or co-sited (2) — a firmware preference. Canon typically writes 2; Nikon and Sony write 1.
Colour channel alignment encoded by this device (1 = centred, 2 = co-sited). Manufacturer-determined — Canon typically writes 2, Nikon and Sony write 1.
| Observed value | |
|---|---|
| 2 |
XMP NamespacesXML namespace URIs present in XMP metadata from this device. The set of namespaces reveals which software pipeline created or processed the file.
XMP namespace URIs present in output from this device.
| Observed value | |
|---|---|
| dc,rdf,x,xmp |
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.
