ImageConver · Browser RAW tool
DNG Metadata Viewer
DNG Metadata Viewer reads Digital Negative (DNG) locally in this browser. Validate the TIFF-based container, read the DNGVersion tag and common TIFF/EXIF directories, count complete JPEG previews, and present the findings locally. It reports the difference between container inspection, embedded JPEG preview extraction, and complete RAW sensor development before you download or rely on a result.
Local RAW inspection
Inspect Digital Negative (DNG) in this browser
Validate the TIFF-based container, read the DNGVersion tag and common TIFF/EXIF directories, count complete JPEG previews, and present the findings locally.
Choose a RAW file to begin.
Direct antwoord
What this RAW tool does
A camera RAW file is a container for sensor samples, camera settings, previews, and manufacturer-specific metadata. Converting it well requires more than changing the extension. Validate the TIFF-based container, read the DNGVersion tag and common TIFF/EXIF directories, count complete JPEG previews, and present the findings locally.
This page focuses on Digital Negative (DNG). The intended output is a DNG and EXIF metadata report. The workflow keeps the source untouched, identifies what the browser can verify, and separates a quick embedded JPEG preview from a rendered image created by a full RAW engine.
DNG permits private data, multiple sub-IFDs, mosaiced sensor samples, linear data, profiles, opcodes, and an optional embedded original. This viewer reads a focused metadata subset and an embedded JPEG preview count. That boundary is important because a preview can open successfully even when the browser has not interpreted the mosaic, white balance coefficients, black level, color matrices, or lens data used for a complete development.
- Input
- Digital Negative (DNG)
- Uitvoer
- a DNG and EXIF metadata report
- Critical limit
- An embedded JPEG preview is not full RAW sensor development.
Werkstroom
How to inspect or convert safely
- 1
Protect the source
Copy the RAW file before testing and note its filename, byte size, camera model, expected dimensions, and capture date. Keep the memory card or primary archive unchanged. A derivative should never be the only remaining copy of a camera negative.
- 2
Process deliberately
Choose the file above. The browser reads its bytes with File and ArrayBuffer APIs, identifies the container, inspects common TIFF/EXIF fields where possible, and searches for a complete embedded JPEG preview. No RAW bytes are sent to an ImageConver conversion endpoint.
- 3
Verify the derivative
Verify the result independently. Compare the embedded JPEG preview or exported image with the camera display and with a full RAW rendering. Check dimensions, color, crop, orientation, metadata, file size, and the application or website that will receive it.
Preview behavior
Embedded JPEG preview versus RAW development
What the preview is
Many RAW files carry one or more JPEG images for the camera display, operating-system thumbnails, catalog browsing, or quick transfer. Extracting the largest embedded JPEG preview can be fast and useful, but its dimensions and quality may be lower than the sensor image.
Why color differs
The preview normally reflects in-camera choices such as picture style, film simulation, white balance, contrast, saturation, sharpening, noise reduction, and lens corrections. A desktop RAW editor can start from different profiles and produce a visibly different interpretation from the same capture.
What re-encoding means
Re-encoding an embedded JPEG preview at a new quality does not restore sensor detail. It creates another JPEG generation from camera-rendered pixels. Keep the original preview bytes when extraction is enough, and use a full RAW engine when editing latitude or maximum quality matters.
Beslissingsgids
Choose the correct RAW workflow
Use the browser tool when you need a quick structural check, readable common metadata, or a camera-generated preview without uploading the file. This is useful for triage, contact sheets, identifying unknown files, and creating a temporary sharing copy.
Use current camera-vendor software when exact picture styles, tethered workflows, or manufacturer-specific lens corrections matter. Use a maintained LibRaw-based application for broad cross-camera support, but verify that its actual bundled LibRaw version supports the camera model.
Use a command-line workflow when conversion must be repeatable across many files. Record software versions, profile names, white balance policy, crop, bit depth, color space, quality, metadata policy, and output naming. Test a representative camera sample before processing an archive.
Rendering quality
Color, detail, and output format
Sensor development
RAW sensor development includes demosaicing for color-filter-array data, camera-to-working-space color conversion, white balance, black-level handling, tone mapping, and often optical corrections. These operations are outside a compact metadata or preview scanner.
Color management
Output color should be chosen for the destination. sRGB is the practical default for general web and application compatibility. Wider-gamut exports require a color-managed destination and an embedded profile. A browser preview alone is not a press-proof or archival color validation.
Choose the derivative
JPEG is appropriate for convenient opaque delivery. TIFF can preserve higher-bit-depth rendered data for editing and print. PNG is lossless for rendered pixels but is not a substitute for RAW controls. The best output depends on the next workflow, not only on file size.
Metagegevens
EXIF, MakerNotes, sidecars, and privacy
Common EXIF fields include make, model, date, exposure time, aperture, ISO, focal length, and lens model. Manufacturer MakerNotes can hold focusing, stabilization, picture-style, serial, and processing details, but their structures differ and can change between camera generations.
Metadata can be duplicated across the RAW container, an embedded JPEG preview, XMP sidecars, and editing catalogs. Conflicting values are possible. For production work, use a mature metadata tool and decide which source is authoritative instead of merging fields blindly.
Location, serial numbers, names, copyright, comments, and workflow identifiers can be sensitive. A newly exported file may omit some fields but should still be checked before sharing. Metadata removal from the original RAW is risky because proprietary information can be required for correct rendering.
Technical detail
How RAW containers and previews are checked
Container identification is the first gate. CR2, NEF, ARW, DNG, and several other formats are TIFF-based but add private tags and structures. CR3 uses an ISO Base Media container. RAF, ORF, and RW2 have their own signatures. Extension-only identification is weaker than matching internal bytes.
A complete JPEG candidate begins with a Start of Image marker, contains valid marker segments, and ends with End of Image. This batch reports complete contiguous candidates and their dimensions. It does not claim to reconstruct previews stored as fragments or proprietary image items.
TIFF directories use byte order, typed values, offsets, and linked image file directories. A safe parser must bounds-check offsets and entry counts before reading. This browser implementation intentionally extracts a small set of standard fields and leaves complex MakerNotes unchanged.
Camera support is model-specific, not only extension-specific. Two files ending in the same extension can use different sensors, compression, pixel layouts, profiles, and metadata revisions. Check the exact camera model against the software version used for final development.
For archival work, retain the original bytes and a checksum. Sidecars or catalog databases should be backed up with the source because edits may not be embedded in the RAW container. Store rendered derivatives separately and label them with output color space and processing date.
Troubleshooting
Common RAW inspection problems
Unknown format
If the tool reports an unknown format, confirm the real extension and signature. Files renamed during transfer, partial downloads, sidecar files, and catalog databases are not camera RAW containers. Recopy the original from trusted storage and compare byte size.
No preview found
If no embedded JPEG preview is found, the file may use a fragmented or proprietary preview structure, store HEIF rather than JPEG, contain only a tiny thumbnail, or be incomplete. Use ExifTool, manufacturer software, or a full RAW library instead of assuming corruption.
Preview differs
If the preview is smaller or looks different, compare its pixel dimensions and recognize that it was rendered by the camera. Develop the sensor data in supported RAW software when you need full resolution, a different white balance, highlight recovery, or another profile.
Metadata missing
If metadata fields are missing, they may live in MakerNotes, a sub-IFD this focused parser does not visit, the embedded JPEG preview, or an XMP sidecar. Missing output from this page is not evidence that the field does not exist anywhere in the RAW workflow.
Privacy
Local file handling
The selected file stays on this device while browser JavaScript reads its bytes. ImageConver does not need to upload the RAW file to perform signature checks, focused TIFF/EXIF parsing, or embedded JPEG preview extraction.
Local processing does not remove device-level risk. Use an approved workstation for confidential photography, retain files in controlled storage, and remove temporary downloads according to policy. Browser-created object URLs are revoked when replaced or the page closes.
An embedded JPEG preview can contain faces, documents, locations, serial information, and other sensitive content even when the RAW sensor data is never developed. Review the derivative and its metadata before sending it to another person or service.
Veelgestelde vragen
DNG Metadata Viewer FAQ
Does this fully develop Digital Negative (DNG) sensor data?
No. Browser tools in this batch inspect container metadata or use an embedded JPEG preview. A full RAW developer applies demosaicing, white balance, camera profiles, tone mapping, noise reduction, and lens corrections to sensor data.
Is the Digital Negative (DNG) file uploaded?
No. The selected file is read with browser File and ArrayBuffer APIs on this device. The tool does not post the RAW bytes to an ImageConver conversion endpoint.
Why can the embedded JPEG preview look different from a desktop RAW editor?
The preview reflects camera processing and picture style, while a RAW editor renders sensor data using its own profile, white balance, tone curve, and corrections.
Will a DNG and EXIF metadata report contain all RAW metadata?
Do not assume so. Extracted or re-encoded derivatives can omit MakerNotes, XMP, GPS, color-profile, and proprietary fields. Keep the original RAW file.
Why is no preview found?
Some files store previews in container structures this compact scanner cannot map, use unsupported compression, encrypt or fragment data, or contain only a small thumbnail. Use current manufacturer software, LibRaw-based software, or ExifTool.
Can I delete the RAW file after downloading?
No. Treat every browser result as a convenient derivative. The RAW file remains the source for higher-quality development, different white balance, stronger highlight recovery, and future software.
Primaire referenties
Specifications and RAW workflow documentation
- Digital Negative (DNG) and DNG specification – Adobe
- TIFF Revision 6.0 specification – Adobe
- Using files from web applications – MDN
- ExifTool application documentation – Phil Harvey
Last reviewed: October 15, 2026. Camera and software support change, so verify the exact camera model against current primary documentation.