realme C53
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.
MakerNote PresenceA proprietary manufacturer block inside EXIF whose format is largely undocumented. Contains settings not in standard EXIF — focus mode, scene detection, lens data, processing flags.
Rate at which this device embeds a MakerNote block (proprietary manufacturer metadata).
Embedded ThumbnailA small JPEG preview stored inside the EXIF APP1 segment, written at capture. May differ from the full image if the file was post-processed.
Rate at which this device embeds a thumbnail in the EXIF APP1 segment.
Output DimensionsImage resolution values (width × height in pixels) observed across analysed files from this device.
Image resolution values observed for this device.
| Observed value | |
|---|---|
| 3072x4080 | |
| 3000x4000 |
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 | |
|---|---|
| APP0JFIF application marker — identifies the file as JFIF format and may carry thumbnail and pixel density info. | |
| APP1Primary metadata container — holds EXIF camera data (make, model, GPS, settings) and optionally XMP. | |
| 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. | |
| SOIStart of Image — the 2-byte marker that opens every valid JPEG file. | |
| SOSStart of Scan — marks the beginning of the compressed image data stream. | |
| 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. |
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 | |
|---|---|
| Exif Version 2.2 | |
| 0220 |
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 | |
|---|---|
| 1 |
Privacy Risk SignalsFields that may contain personally-identifying information. Presence rate is shown; individual values are never stored or displayed.
Rate at which files from this device contained personally identifying metadata fields. Individual values are never shown.
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.
