Drop files or choose a source
Upload multiple files at once, mix formats, and fine-tune every conversion with format-aware settings.
Max 2GB per file · Drag & drop ready · Mixed file types welcome
Format hubs
Explore 322 formats with conversion options and metadata.
IMAGE
3FR
3fr
## Overview 3FR matters because Hasselblad medium-format workflows prioritize raw capture quality, color fidelity, and studio-grade post-production flexibility rather than lightweight consumer delivery. Photography workflows needed a way to preserve sensor data and capture metadata before white balance, sharpening, tonal rendering, or lossy compression choices became permanent. 3FR appears mainly in high-end commercial, studio, and medium-format archival workflows before export into DNG, TIFF, PSD, or delivery images. 3FR is closely associated with Hasselblad. 3FR is usually selected for workflows that center on capture ingest, editing, web or print delivery. ## Typical Workflows - capture ingest - editing - web or print delivery ## Common Software - vendor photo software - Adobe Camera Raw - LibRaw-based workflows ## Strengths - Preserve capture-stage sensor information. - Support deeper photo-editing and archival workflows than flattened delivery images. - Retain metadata and workflow latitude that rendered outputs usually discard. ## Limitations - Compatibility often depends on vendor or decoder support. - They are source formats, not publication-ready outputs. - Public technical documentation is uneven across manufacturers. ## Related Formats - DNG - JPG - TIFF - PNG ## Interesting Context Hasselblad raw workflows are closely tied to medium-format capture and to the brand's studio and commercial-photography lineage, which gives 3FR a different practical role from mass-market DSLR raw families.
IMAGE
APNG
apng
## Overview APNG matters because it extends PNG-style lossless imaging and alpha transparency into lightweight animation, giving teams an option when GIF is too limited and video is too heavyweight for the workflow. Web teams wanted animation that could preserve full alpha transparency and PNG-style image quality without forcing every asset into video containers. APNG is mainly used for short looped UI, product, or motion assets where alpha-aware browser delivery matters more than universal legacy support. APNG is closely associated with W3C PNG working group / Mozilla-origin extension lineage. APNG is usually selected for workflows that center on capture ingest, editing, web or print delivery. ## Typical Workflows - capture ingest - editing - web or print delivery ## Common Software - browser engines - ImageMagick - design export pipelines ## Strengths - Supports animation while keeping PNG-style lossless imaging. - Retains alpha transparency in ways GIF cannot. - Fits browser-facing workflows better than heavyweight video for some small loops. ## Limitations - Larger payloads than newer video-style delivery can be common. - Not every downstream tool treats animated PNG as a first-class editing format. - Animation-focused targets may still require playback validation after conversion. ## Related Formats - PNG - GIF - WEBP - AVIF ## Interesting Context APNG started as a Mozilla-driven attempt to bring better animation into the PNG ecosystem. Its practical relevance increased once modern browsers and toolchains treated it as a viable web animation target.
IMAGE
ARI
ari
## Overview These proprietary camera raw formats matter because serious photography workflows often begin in camera-native sensor data, and that means conversion decisions are shaped by manufacturer-specific raw semantics long before the file becomes a general-purpose image. Camera makers needed formats that could preserve sensor data and capture metadata before irreversible rendering choices such as white balance, sharpening, or final compression were baked into delivery images. Vendor raw formats remain central to photo ingestion, editing, archiving, and conversion workflows even when final delivery happens as JPG, TIFF, PNG, or DNG. ARI is closely associated with camera-vendor raw ecosystems decoded today through the LibRaw/dcraw lineage. ARI is usually selected for workflows that center on capture ingest, editing, web or print delivery. ## Typical Workflows - capture ingest - editing - web or print delivery ## Common Software - LibRaw - Adobe Camera Raw - vendor photo software - archive workflows ## Strengths - Preserve capture-stage image data for later interpretation. - Useful for high-end photo editing, archival masters, and sensor-aware workflows. - Maintain metadata and capture flexibility that rendered delivery formats usually cannot. ## Limitations - Many are vendor-specific and poorly documented publicly. - Compatibility often depends on decoder support in tools such as LibRaw, Adobe Camera Raw, or vendor software. - They are source formats, not publication-ready outputs. ## Related Formats - DNG - JPG - TIFF - PNG ## Interesting Context Digital photography fragmented into many manufacturer-specific raw formats because camera makers optimized for their own sensors, metadata, and software ecosystems rather than for one shared public raw standard.
IMAGE
JPS
jps
## Overview JPS matters because stereoscopic image workflows needed a lightweight way to package left-eye and right-eye views inside familiar JPEG-compatible handling paths. Stereo imaging tools needed a simple deliverable that could keep paired views together while staying close to mainstream JPEG and Exif handling. JPS now appears mostly in legacy 3D-photo collections, compatibility playback, and migration workflows that normalize stereoscopic still images into more current containers or viewer-specific formats. JPS is closely associated with Stereoscopic imaging community. JPS is usually selected for workflows that center on capture ingest, editing, web or print delivery. ## Typical Workflows - capture ingest - editing - web or print delivery ## Common Software - legacy 3D viewers - stereo-photo tools - media players with stereoscopic support ## Strengths - Simple side-by-side packaging on top of familiar JPEG decoding. - Useful in legacy stereo-photo device and display workflows. - Easy to preserve as an ordinary image file with extra stereoscopic interpretation. ## Limitations - Not a rich or broadly standardized 3D still-image format. - Receiving software often needs explicit stereoscopic awareness to do the right thing. - Usually less flexible than newer multi-image or depth-aware approaches. ## Related Formats - JPG - MPO - PNG - JXR ## Interesting Context JPS belongs to the period when consumer 3D displays, cameras, and media players experimented with stereo-photo conventions built on ordinary JPEG assets instead of inventing entirely new everyday imaging stacks.
IMAGE
ARW
arw
## Overview ARW matters because Sony's Alpha ecosystem became one of the major modern interchangeable-lens camera platforms, which made Sony raw support a practical requirement across consumer, enthusiast, and professional photo software. Photography workflows needed a way to preserve sensor data and capture metadata before white balance, sharpening, tonal rendering, or lossy compression choices became permanent. ARW is now a mainstream contemporary raw family in editing, archive, and hybrid photo/video creator workflows before export into DNG, TIFF, JPEG, or web delivery formats. ARW is closely associated with Sony. ARW is usually selected for workflows that center on capture ingest, editing, web or print delivery. ## Typical Workflows - capture ingest - editing - web or print delivery ## Common Software - vendor photo software - Adobe Camera Raw - LibRaw-based workflows ## Strengths - Preserve capture-stage sensor information. - Support deeper photo-editing and archival workflows than flattened delivery images. - Retain metadata and workflow latitude that rendered outputs usually discard. ## Limitations - Compatibility often depends on vendor or decoder support. - They are source formats, not publication-ready outputs. - Public technical documentation is uneven across manufacturers. ## Related Formats - DNG - JPG - TIFF - PNG ## Interesting Context As Sony expanded from consumer electronics into serious camera bodies and sensors, ARW became part of the broader shift that put Sony raw support on the critical path for many photo applications.
IMAGE
AVIF
avif
## Overview AVIF matters because it brings modern AV1 compression efficiency to still images in a packaging model designed for advanced image features, making it attractive for bandwidth-sensitive web and mobile delivery. Publishers needed image delivery formats that could substantially reduce payload size while still supporting higher efficiency and newer imaging features than older web defaults. AVIF is increasingly used for modern web and mobile image delivery where download size and compression efficiency matter more than legacy-tool compatibility. AVIF is closely associated with Alliance for Open Media. AVIF is usually selected for workflows that center on capture ingest, editing, web or print delivery. ## Typical Workflows - capture ingest - editing - web or print delivery ## Common Software - Modern browsers - ImageMagick - mobile/web delivery stacks ## Strengths - Very strong compression efficiency for many image workloads. - Modern feature set built on a newer image-container model. - Attractive for web delivery and responsive imaging pipelines. ## Limitations - Encoding complexity and tooling support are still less frictionless than older formats in some environments. - Older software and enterprise pipelines may not treat it as a first-class editing format. ## Related Formats - WEBP - JPG - PNG - HEIF ## Interesting Context AVIF emerged from the Alliance for Open Media's work around AV1 and uses the HEIF family as its structural container, which connects it to both modern web delivery and newer image-container design.
IMAGE
BAY
bay
## Overview These proprietary camera raw formats matter because serious photography workflows often begin in camera-native sensor data, and that means conversion decisions are shaped by manufacturer-specific raw semantics long before the file becomes a general-purpose image. Camera makers needed formats that could preserve sensor data and capture metadata before irreversible rendering choices such as white balance, sharpening, or final compression were baked into delivery images. Vendor raw formats remain central to photo ingestion, editing, archiving, and conversion workflows even when final delivery happens as JPG, TIFF, PNG, or DNG. BAY is closely associated with camera-vendor raw ecosystems decoded today through the LibRaw/dcraw lineage. BAY is usually selected for workflows that center on capture ingest, editing, web or print delivery. ## Typical Workflows - capture ingest - editing - web or print delivery ## Common Software - LibRaw - Adobe Camera Raw - vendor photo software - archive workflows ## Strengths - Preserve capture-stage image data for later interpretation. - Useful for high-end photo editing, archival masters, and sensor-aware workflows. - Maintain metadata and capture flexibility that rendered delivery formats usually cannot. ## Limitations - Many are vendor-specific and poorly documented publicly. - Compatibility often depends on decoder support in tools such as LibRaw, Adobe Camera Raw, or vendor software. - They are source formats, not publication-ready outputs. ## Related Formats - DNG - JPG - TIFF - PNG ## Interesting Context Digital photography fragmented into many manufacturer-specific raw formats because camera makers optimized for their own sensors, metadata, and software ecosystems rather than for one shared public raw standard.
IMAGE
BMP
bmp
## Overview BMP matters mostly as a straightforward Windows-native bitmap family: it is easy to decode, historically important in desktop software, and still useful when simple unambiguous raster interchange matters more than compression efficiency. Windows applications needed a simple native bitmap representation that the operating system and graphics APIs could read and write with minimal ceremony. BMP is now mainly a compatibility and intermediate format for legacy desktop, testing, and simple raster workflows where file size is not the priority. BMP is closely associated with Microsoft / Windows graphics stack. BMP is usually selected for workflows that center on capture ingest, editing, web or print delivery. ## Typical Workflows - capture ingest - editing - web or print delivery ## Common Software - Windows imaging tools - Paint - ImageMagick ## Strengths - Very easy for software to decode and inspect. - Commonly supported in Windows-oriented and general-purpose graphics tools. - Useful when you want a straightforward raster container without complex delivery tuning. ## Limitations - Files are often much larger than modern delivery formats. - It is a weak choice for web publishing or bandwidth-sensitive distribution. ## Related Formats - PNG - JPG - TIFF - ICO ## Interesting Context Bitmap and device-independent bitmap structures became part of the Windows graphics story early in the platform's life, which is why BMP still appears in older desktop workflows and low-friction image interchange tasks.
IMAGE
BPG
bpg
## Overview BPG matters because it was an explicit attempt to replace JPEG with a more compression-efficient still-image format while keeping practical image features such as alpha, metadata, higher bit depths, and optional animation. Publishers wanted a still-image format that could beat JPEG on quality-per-byte without discarding common image features or forcing every asset into a video container. BPG is now mostly a niche technical and conversion format, but it remains a useful historical reference point in the search for better general-purpose still-image compression. BPG is closely associated with Fabrice Bellard. BPG is usually selected for workflows that center on capture ingest, editing, web or print delivery. ## Typical Workflows - capture ingest - editing - web or print delivery ## Common Software - ImageMagick - BPG encoder/decoder tools - technical conversion workflows ## Strengths - Higher compression efficiency than legacy JPEG in many cases. - Supports alpha, metadata, animation, and higher bit depths. - Designed to preserve still-image workflow expectations rather than only video playback assumptions. ## Limitations - Never achieved the browser, device, or platform support needed for mainstream adoption. - Strong HEVC lineage complicated the format's practical ecosystem story. - Usually appears today as a conversion edge case rather than a preferred delivery target. ## Related Formats - JPG - PNG - WEBP - AVIF ## Interesting Context BPG arrived in the mid-2010s when image engineers were looking for better post-JPEG compression before AVIF and JPEG XL had ecosystem momentum.
IMAGE
CAP
cap
## Overview These proprietary camera raw formats matter because serious photography workflows often begin in camera-native sensor data, and that means conversion decisions are shaped by manufacturer-specific raw semantics long before the file becomes a general-purpose image. Camera makers needed formats that could preserve sensor data and capture metadata before irreversible rendering choices such as white balance, sharpening, or final compression were baked into delivery images. Vendor raw formats remain central to photo ingestion, editing, archiving, and conversion workflows even when final delivery happens as JPG, TIFF, PNG, or DNG. CAP is closely associated with camera-vendor raw ecosystems decoded today through the LibRaw/dcraw lineage. CAP is usually selected for workflows that center on capture ingest, editing, web or print delivery. ## Typical Workflows - capture ingest - editing - web or print delivery ## Common Software - LibRaw - Adobe Camera Raw - vendor photo software - archive workflows ## Strengths - Preserve capture-stage image data for later interpretation. - Useful for high-end photo editing, archival masters, and sensor-aware workflows. - Maintain metadata and capture flexibility that rendered delivery formats usually cannot. ## Limitations - Many are vendor-specific and poorly documented publicly. - Compatibility often depends on decoder support in tools such as LibRaw, Adobe Camera Raw, or vendor software. - They are source formats, not publication-ready outputs. ## Related Formats - DNG - JPG - TIFF - PNG ## Interesting Context Digital photography fragmented into many manufacturer-specific raw formats because camera makers optimized for their own sensors, metadata, and software ecosystems rather than for one shared public raw standard.
IMAGE
CIN
cin
## Overview CIN matters because it belongs to the older digital-film scanning and visual-effects lineage that shaped how high-end moving-image workflows handled log-encoded frame images before later exchange formats became more dominant. Film scanning and early digital post-production needed a frame-based image format suited to log-encoded motion-picture workflows. CIN now appears mainly in legacy film/VFX archives and compatibility conversions. CIN is closely associated with Kodak Cineon lineage. CIN is usually selected for workflows that center on capture ingest, editing, web or print delivery. ## Typical Workflows - capture ingest - editing - web or print delivery ## Common Software - VFX pipelines - legacy film workflows - ImageMagick ## Strengths - Historically important in film-scanning and early digital post pipelines. - Useful when migrating older production assets. ## Limitations - Long-tail compatibility format rather than a mainstream modern choice. - Usually converted onward into more current production or archive formats. ## Related Formats - DPX - EXR - TIFF ## Interesting Context The Cineon format comes from Kodak's film-to-digital ecosystem and directly influences the later professional frame-exchange story around DPX.
IMAGE
JPEG 2000
jpx, jpf
## Overview JPX matters because it extends basic JP2 packaging with multiple codestreams, richer metadata, more flexible composition, broader colour handling, and other features needed in complex professional imaging workflows. Advanced imaging workflows wanted more expressive file-format capabilities than core JP2 offered, including richer composition, metadata, and multi-codestream structures. JPX remains a specialist JPEG 2000 family format used where the extra file-format flexibility matters more than mainstream browser or consumer-software reach. JPEG 2000 is closely associated with ISO/IEC JTC 1/SC 29. JPEG 2000 is usually selected for workflows that center on capture ingest, editing, web or print delivery. ## Typical Workflows - capture ingest - editing - web or print delivery ## Common Software - OpenJPEG - institutional imaging tools - JPEG 2000 workflows ## Strengths - Richer packaging than baseline JP2. - Supports complex colour, metadata, and composition needs. - Fits advanced institutional and professional imaging scenarios better than ordinary consumer formats. ## Limitations - Even more niche than basic JPEG 2000 in everyday tooling. - Complexity and uneven support limit casual interoperability. - Usually appears in specialist pipelines rather than general-purpose publishing. ## Related Formats - JP2 - J2K - JPM - JXR ## Interesting Context JPX reflects the branch of JPEG 2000 that pushed beyond a simple still-image wrapper into more expressive composition and metadata scenarios for professional and institutional imaging.
IMAGE
CR2
cr2
## Overview CR2 matters because Canon's EOS ecosystem became one of the largest digital-camera platforms in the world, which made Canon raw support essential across newsroom, studio, event, and enthusiast editing software. Photography workflows needed a way to preserve sensor data and capture metadata before white balance, sharpening, tonal rendering, or lossy compression choices became permanent. CR2 remains a major archival and editing raw format in Canon-centered photo libraries even as newer bodies increasingly shifted into CR3. CR2 is closely associated with Canon. CR2 is usually selected for workflows that center on capture ingest, editing, web or print delivery. ## Typical Workflows - capture ingest - editing - web or print delivery ## Common Software - vendor photo software - Adobe Camera Raw - LibRaw-based workflows ## Strengths - Preserve capture-stage sensor information. - Support deeper photo-editing and archival workflows than flattened delivery images. - Retain metadata and workflow latitude that rendered outputs usually discard. ## Limitations - Compatibility often depends on vendor or decoder support. - They are source formats, not publication-ready outputs. - Public technical documentation is uneven across manufacturers. ## Related Formats - DNG - JPG - TIFF - PNG ## Interesting Context CR2 became the dominant Canon raw family through the long DSLR era, so huge real-world photo archives still depend on stable CR2 decoding and migration paths.
IMAGE
CR3
cr3
## Overview CR3 matters because it is Canon's newer raw generation for modern EOS and PowerShot cameras, tying contemporary Canon capture workflows to updated raw handling and software support expectations. Photography workflows needed a way to preserve sensor data and capture metadata before white balance, sharpening, tonal rendering, or lossy compression choices became permanent. CR3 is now a current Canon raw family in modern creator, enthusiast, and professional workflows before export into DNG, TIFF, JPEG, or delivery assets. CR3 is closely associated with Canon. CR3 is usually selected for workflows that center on capture ingest, editing, web or print delivery. ## Typical Workflows - capture ingest - editing - web or print delivery ## Common Software - vendor photo software - Adobe Camera Raw - LibRaw-based workflows ## Strengths - Preserve capture-stage sensor information. - Support deeper photo-editing and archival workflows than flattened delivery images. - Retain metadata and workflow latitude that rendered outputs usually discard. ## Limitations - Compatibility often depends on vendor or decoder support. - They are source formats, not publication-ready outputs. - Public technical documentation is uneven across manufacturers. ## Related Formats - DNG - JPG - TIFF - PNG ## Interesting Context CR3 marks Canon's move into a newer raw-file generation as mirrorless and later-camera workflows evolved beyond the long CR2 era.
IMAGE
CRW
crw
## Overview CRW matters historically because it belongs to Canon's earlier raw era before CR2 and CR3, and older photo archives still surface it in migration work. Photography workflows needed a way to preserve sensor data and capture metadata before white balance, sharpening, tonal rendering, or lossy compression choices became permanent. CRW is now primarily a legacy Canon raw format that matters in archive recovery and conversion. CRW is closely associated with Canon. CRW is usually selected for workflows that center on capture ingest, editing, web or print delivery. ## Typical Workflows - capture ingest - editing - web or print delivery ## Common Software - vendor photo software - Adobe Camera Raw - LibRaw-based workflows ## Strengths - Preserve capture-stage sensor information. - Support deeper photo-editing and archival workflows than flattened delivery images. - Retain metadata and workflow latitude that rendered outputs usually discard. ## Limitations - Compatibility often depends on vendor or decoder support. - They are source formats, not publication-ready outputs. - Public technical documentation is uneven across manufacturers. ## Related Formats - DNG - JPG - TIFF - PNG ## Interesting Context Early Canon digital-camera workflows used raw formats like CRW before the later EOS raw families stabilized around CR2 and then CR3.
IMAGE
CUR
cur
## Overview CUR and DIB matter because operating systems often need raster formats tailored to specific UI resource and device-independent graphics behavior rather than to general-purpose image publishing. Windows needed graphics resource formats that could support UI assets and device-independent display behavior inside the operating system and application stack. They now appear mostly in compatibility, UI-resource, and conversion workflows tied to Windows graphics history. CUR is closely associated with Microsoft / Windows graphics ecosystem. CUR is usually selected for workflows that center on capture ingest, editing, web or print delivery. ## Typical Workflows - capture ingest - editing - web or print delivery ## Common Software - Windows resource tools - ImageMagick - compatibility workflows ## Strengths - Relevant for Windows resource compatibility. - Useful when preserving or transforming UI-related graphics assets. ## Limitations - Not mainstream web or publishing image targets. - The workflow value is strongly platform-specific. ## Related Formats - ICO - ICNS - PNG - BMP ## Interesting Context These formats reflect how desktop operating systems built their own graphics-resource conventions for cursors, icons, and device-independent drawing.
IMAGE
DCM
dcm
## Overview DCM matters because DICOM files are not just pictures; they are part of a clinical-imaging standard that packages image payloads together with patient, study, device, and workflow metadata needed in medical systems. Healthcare imaging workflows needed files that could carry both image data and the metadata required for safe interchange across modalities, workstations, and archival systems. DICOM remains the core interchange and storage format for medical imaging, and it appears in conversion work mainly when image data must move into or out of clinical workflows. DCM is closely associated with DICOM Standards Committee / NEMA. DCM is usually selected for workflows that center on capture ingest, editing, web or print delivery. ## Typical Workflows - capture ingest - editing - web or print delivery ## Common Software - clinical viewers - PACS - medical-imaging toolchains ## Strengths - Carries workflow-critical metadata alongside image content. - Deeply embedded in clinical imaging and PACS environments. - Supports interchange needs that general consumer image formats do not address. ## Limitations - Not a general-purpose image target for ordinary publishing. - Validation has to include metadata and receiving-system behavior, not just visual output. ## Related Formats - PNG - TIFF - DJVU ## Interesting Context DICOM grew out of the need to exchange imaging data across scanners, archives, and clinical systems without throwing away the surrounding context that makes a medical image usable in practice.
IMAGE
DCR
dcr
## Overview These proprietary camera raw formats matter because serious photography workflows often begin in camera-native sensor data, and that means conversion decisions are shaped by manufacturer-specific raw semantics long before the file becomes a general-purpose image. Camera makers needed formats that could preserve sensor data and capture metadata before irreversible rendering choices such as white balance, sharpening, or final compression were baked into delivery images. Vendor raw formats remain central to photo ingestion, editing, archiving, and conversion workflows even when final delivery happens as JPG, TIFF, PNG, or DNG. DCR is closely associated with camera-vendor raw ecosystems decoded today through the LibRaw/dcraw lineage. DCR is usually selected for workflows that center on capture ingest, editing, web or print delivery. ## Typical Workflows - capture ingest - editing - web or print delivery ## Common Software - LibRaw - Adobe Camera Raw - vendor photo software - archive workflows ## Strengths - Preserve capture-stage image data for later interpretation. - Useful for high-end photo editing, archival masters, and sensor-aware workflows. - Maintain metadata and capture flexibility that rendered delivery formats usually cannot. ## Limitations - Many are vendor-specific and poorly documented publicly. - Compatibility often depends on decoder support in tools such as LibRaw, Adobe Camera Raw, or vendor software. - They are source formats, not publication-ready outputs. ## Related Formats - DNG - JPG - TIFF - PNG ## Interesting Context Digital photography fragmented into many manufacturer-specific raw formats because camera makers optimized for their own sensors, metadata, and software ecosystems rather than for one shared public raw standard.
IMAGE
DCS
dcs
## Overview These proprietary camera raw formats matter because serious photography workflows often begin in camera-native sensor data, and that means conversion decisions are shaped by manufacturer-specific raw semantics long before the file becomes a general-purpose image. Camera makers needed formats that could preserve sensor data and capture metadata before irreversible rendering choices such as white balance, sharpening, or final compression were baked into delivery images. Vendor raw formats remain central to photo ingestion, editing, archiving, and conversion workflows even when final delivery happens as JPG, TIFF, PNG, or DNG. DCS is closely associated with camera-vendor raw ecosystems decoded today through the LibRaw/dcraw lineage. DCS is usually selected for workflows that center on capture ingest, editing, web or print delivery. ## Typical Workflows - capture ingest - editing - web or print delivery ## Common Software - LibRaw - Adobe Camera Raw - vendor photo software - archive workflows ## Strengths - Preserve capture-stage image data for later interpretation. - Useful for high-end photo editing, archival masters, and sensor-aware workflows. - Maintain metadata and capture flexibility that rendered delivery formats usually cannot. ## Limitations - Many are vendor-specific and poorly documented publicly. - Compatibility often depends on decoder support in tools such as LibRaw, Adobe Camera Raw, or vendor software. - They are source formats, not publication-ready outputs. ## Related Formats - DNG - JPG - TIFF - PNG ## Interesting Context Digital photography fragmented into many manufacturer-specific raw formats because camera makers optimized for their own sensors, metadata, and software ecosystems rather than for one shared public raw standard.
IMAGE
DDS
dds
## Overview DDS matters because real-time graphics pipelines often care about GPU-oriented texture storage, compression, mipmaps, and engine compatibility rather than about general-purpose image editing or web publishing. Game and graphics pipelines needed a texture format that could package GPU-relevant data such as mipmaps and compressed texture layouts efficiently. DDS remains common in game assets, modding, engines, and technical texture pipelines. DDS is closely associated with Microsoft / DirectX ecosystem. DDS is usually selected for workflows that center on capture ingest, editing, web or print delivery. ## Typical Workflows - capture ingest - editing - web or print delivery ## Common Software - DirectX tools - game engines - texture workflows ## Strengths - Suited to GPU and game-texture workflows. - Can package texture-specific details such as mipmaps. - Useful technical interchange target for graphics-engine stacks. ## Limitations - Poor fit for ordinary browser or office image workflows. - Visual validation alone can miss engine-specific texture expectations. ## Related Formats - PNG - TGA - BMP ## Interesting Context DDS grew out of Microsoft's graphics API and game-development ecosystem, which is why it feels more like an engine or texture-delivery format than a conventional consumer image file.
IMAGE
DIB
dib
## Overview CUR and DIB matter because operating systems often need raster formats tailored to specific UI resource and device-independent graphics behavior rather than to general-purpose image publishing. Windows needed graphics resource formats that could support UI assets and device-independent display behavior inside the operating system and application stack. They now appear mostly in compatibility, UI-resource, and conversion workflows tied to Windows graphics history. DIB is closely associated with Microsoft / Windows graphics ecosystem. DIB is usually selected for workflows that center on capture ingest, editing, web or print delivery. ## Typical Workflows - capture ingest - editing - web or print delivery ## Common Software - Windows resource tools - ImageMagick - compatibility workflows ## Strengths - Relevant for Windows resource compatibility. - Useful when preserving or transforming UI-related graphics assets. ## Limitations - Not mainstream web or publishing image targets. - The workflow value is strongly platform-specific. ## Related Formats - ICO - ICNS - PNG - BMP ## Interesting Context These formats reflect how desktop operating systems built their own graphics-resource conventions for cursors, icons, and device-independent drawing.
IMAGE
DNG
dng
## Overview DNG matters because Adobe created it as a publicly documented camera-raw format to reduce the long-term preservation and interoperability risks of proprietary manufacturer raw files. Photographers and software vendors needed a documented raw-image format that could be archived, shared, and supported without reverse-engineering every camera maker's private raw design. DNG is used as both a native raw format on some devices and a normalization target when photographers want a more openly documented archival raw master. DNG is closely associated with Adobe. DNG is usually selected for workflows that center on capture ingest, editing, web or print delivery. ## Typical Workflows - capture ingest - editing - web or print delivery ## Common Software - Adobe Camera Raw - Lightroom - raw-processing and archive workflows ## Strengths - Publicly documented raw format with broad software support. - Useful archival target when proprietary raw longevity is a concern. - Carries raw-image semantics rather than flattening immediately into rendered pixels. ## Limitations - Not every workflow wants an extra normalization step away from the camera-native original. - Some vendor-specific metadata or processing behavior can remain ecosystem-specific even when the container is DNG. ## Related Formats - CR2 - CR3 - NEF - ARW ## Interesting Context DNG emerged when professional photo workflows were already fragmented across many undocumented vendor raw formats. Adobe positioned it as a common archival and interchange option rather than just another camera-native format.
IMAGE
DPX
dpx
## Overview DPX matters because it became one of the classic high-fidelity frame-based exchange formats in film scanning, visual effects, finishing, and preservation workflows where single images represent pieces of a motion pipeline rather than standalone pictures. Film and post-production workflows needed a dependable way to exchange high-quality image sequences and associated metadata between scanning, grading, compositing, and finishing systems. DPX still appears in film restoration, VFX, finishing, and archival pipelines where frame sequences and fidelity matter more than lightweight delivery. DPX is closely associated with SMPTE. DPX is usually selected for workflows that center on capture ingest, editing, web or print delivery. ## Typical Workflows - capture ingest - editing - web or print delivery ## Common Software - VFX tools - grading systems - preservation workflows ## Strengths - Strong fit for image-sequence workflows in post-production. - Carries metadata relevant to professional moving-image pipelines. - Common archival and interchange choice in frame-based cinema workflows. ## Limitations - Not intended as a casual web or consumer image format. - Usually much heavier than mainstream delivery targets. ## Related Formats - CIN - EXR - TIFF - HDR ## Interesting Context DPX inherits part of the motion-picture scanning and Kodak/Cineon lineage, then becomes formalized as a SMPTE exchange format for professional moving-image work.
IMAGE
DRF
drf
## Overview These proprietary camera raw formats matter because serious photography workflows often begin in camera-native sensor data, and that means conversion decisions are shaped by manufacturer-specific raw semantics long before the file becomes a general-purpose image. Camera makers needed formats that could preserve sensor data and capture metadata before irreversible rendering choices such as white balance, sharpening, or final compression were baked into delivery images. Vendor raw formats remain central to photo ingestion, editing, archiving, and conversion workflows even when final delivery happens as JPG, TIFF, PNG, or DNG. DRF is closely associated with camera-vendor raw ecosystems decoded today through the LibRaw/dcraw lineage. DRF is usually selected for workflows that center on capture ingest, editing, web or print delivery. ## Typical Workflows - capture ingest - editing - web or print delivery ## Common Software - LibRaw - Adobe Camera Raw - vendor photo software - archive workflows ## Strengths - Preserve capture-stage image data for later interpretation. - Useful for high-end photo editing, archival masters, and sensor-aware workflows. - Maintain metadata and capture flexibility that rendered delivery formats usually cannot. ## Limitations - Many are vendor-specific and poorly documented publicly. - Compatibility often depends on decoder support in tools such as LibRaw, Adobe Camera Raw, or vendor software. - They are source formats, not publication-ready outputs. ## Related Formats - DNG - JPG - TIFF - PNG ## Interesting Context Digital photography fragmented into many manufacturer-specific raw formats because camera makers optimized for their own sensors, metadata, and software ecosystems rather than for one shared public raw standard.
IMAGE
EIP
eip
## Overview These proprietary camera raw formats matter because serious photography workflows often begin in camera-native sensor data, and that means conversion decisions are shaped by manufacturer-specific raw semantics long before the file becomes a general-purpose image. Camera makers needed formats that could preserve sensor data and capture metadata before irreversible rendering choices such as white balance, sharpening, or final compression were baked into delivery images. Vendor raw formats remain central to photo ingestion, editing, archiving, and conversion workflows even when final delivery happens as JPG, TIFF, PNG, or DNG. EIP is closely associated with camera-vendor raw ecosystems decoded today through the LibRaw/dcraw lineage. EIP is usually selected for workflows that center on capture ingest, editing, web or print delivery. ## Typical Workflows - capture ingest - editing - web or print delivery ## Common Software - LibRaw - Adobe Camera Raw - vendor photo software - archive workflows ## Strengths - Preserve capture-stage image data for later interpretation. - Useful for high-end photo editing, archival masters, and sensor-aware workflows. - Maintain metadata and capture flexibility that rendered delivery formats usually cannot. ## Limitations - Many are vendor-specific and poorly documented publicly. - Compatibility often depends on decoder support in tools such as LibRaw, Adobe Camera Raw, or vendor software. - They are source formats, not publication-ready outputs. ## Related Formats - DNG - JPG - TIFF - PNG ## Interesting Context Digital photography fragmented into many manufacturer-specific raw formats because camera makers optimized for their own sensors, metadata, and software ecosystems rather than for one shared public raw standard.
IMAGE
EPS
eps
## Overview EPS matters because it was one of the classic ways to move scalable graphics and print-ready artwork between design, illustration, and page-layout tools during the rise of desktop publishing. Designers and publishers needed a way to encapsulate graphics so they could be placed into documents and sent through professional print pipelines. EPS remains relevant in some legacy print and illustration workflows, although PDF and newer formats have displaced it in many modern environments. EPS is closely associated with Adobe PostScript graphics ecosystem. EPS is usually selected for workflows that center on capture ingest, editing, web or print delivery. ## Typical Workflows - capture ingest - editing - web or print delivery ## Common Software - Illustrator - InDesign - prepress tools - Ghostscript ## Strengths - Historically strong fit for professional print workflows. - Useful for scalable artwork and placed graphics. - Deep compatibility with older publishing and prepress tooling. ## Limitations - Modern collaborative and browser-native workflows usually prefer newer formats. - Editing and preview behavior can be awkward outside specialist graphics tools. ## Related Formats - PS - PDF - SVG - TIFF ## Interesting Context Adobe introduced EPS in the late 1980s to make it easier to place graphics and illustrations into larger publishing workflows while retaining PostScript-based print fidelity.
IMAGE
ERF
erf
## Overview These proprietary camera raw formats matter because serious photography workflows often begin in camera-native sensor data, and that means conversion decisions are shaped by manufacturer-specific raw semantics long before the file becomes a general-purpose image. Camera makers needed formats that could preserve sensor data and capture metadata before irreversible rendering choices such as white balance, sharpening, or final compression were baked into delivery images. Vendor raw formats remain central to photo ingestion, editing, archiving, and conversion workflows even when final delivery happens as JPG, TIFF, PNG, or DNG. ERF is closely associated with camera-vendor raw ecosystems decoded today through the LibRaw/dcraw lineage. ERF is usually selected for workflows that center on capture ingest, editing, web or print delivery. ## Typical Workflows - capture ingest - editing - web or print delivery ## Common Software - LibRaw - Adobe Camera Raw - vendor photo software - archive workflows ## Strengths - Preserve capture-stage image data for later interpretation. - Useful for high-end photo editing, archival masters, and sensor-aware workflows. - Maintain metadata and capture flexibility that rendered delivery formats usually cannot. ## Limitations - Many are vendor-specific and poorly documented publicly. - Compatibility often depends on decoder support in tools such as LibRaw, Adobe Camera Raw, or vendor software. - They are source formats, not publication-ready outputs. ## Related Formats - DNG - JPG - TIFF - PNG ## Interesting Context Digital photography fragmented into many manufacturer-specific raw formats because camera makers optimized for their own sensors, metadata, and software ecosystems rather than for one shared public raw standard.
IMAGE
EXR
exr
## Overview OpenEXR matters because it became the professional-grade HDR image format for film, VFX, and rendering workflows that need scene-referred data, deep precision, and production-oriented metadata beyond consumer image expectations. Production imaging teams needed an image format that could store wide dynamic range, high precision, and rich metadata without collapsing everything into consumer-display assumptions. EXR is central in rendering, compositing, and HDR/VFX pipelines where scene-linear or otherwise precision-heavy image data needs to survive interchange. EXR is closely associated with Academy Software Foundation / OpenEXR community. EXR is usually selected for workflows that center on capture ingest, editing, web or print delivery. ## Typical Workflows - capture ingest - editing - web or print delivery ## Common Software - OpenEXR tools - renderers - compositors - VFX pipelines ## Strengths - Designed for HDR and production-grade image precision. - Widely accepted in VFX and rendering ecosystems. - Handles richer technical imaging needs than consumer formats. ## Limitations - Not appropriate for lightweight general-purpose delivery. - Needs target-aware validation because viewers and editors may handle EXR differently. ## Related Formats - HDR - DPX - CIN - TIFF ## Interesting Context OpenEXR came from film-production needs at ILM and then evolved into an open industry format that spread across rendering, compositing, and broader high-end image pipelines.
IMAGE
FFF
fff
## Overview FFF matters because it belongs to Hasselblad's high-end raw and processing ecosystem, where preserving medium-format capture fidelity and downstream studio-editing flexibility matters more than mass-market interchange. Photography workflows needed a way to preserve sensor data and capture metadata before white balance, sharpening, tonal rendering, or lossy compression choices became permanent. FFF is mostly encountered in professional Hasselblad/Phocus workflows and in migration projects that need to preserve or normalize older medium-format raw assets. FFF is closely associated with Hasselblad / Phocus workflow. FFF is usually selected for workflows that center on capture ingest, editing, web or print delivery. ## Typical Workflows - capture ingest - editing - web or print delivery ## Common Software - vendor photo software - Adobe Camera Raw - LibRaw-based workflows ## Strengths - Preserve capture-stage sensor information. - Support deeper photo-editing and archival workflows than flattened delivery images. - Retain metadata and workflow latitude that rendered outputs usually discard. ## Limitations - Compatibility often depends on vendor or decoder support. - They are source formats, not publication-ready outputs. - Public technical documentation is uneven across manufacturers. ## Related Formats - 3FR - TIFF - PSD ## Interesting Context Hasselblad's workflow tooling treated raw capture and high-end processing as parts of one integrated medium-format imaging environment, which is why formats like FFF survive in specialist archives.
IMAGE
FITS
fits
## Overview FITS matters because astronomy and related scientific imaging need a format that treats images as scientific data products with headers, coordinate metadata, and analysis context rather than as ordinary pictures for display. Scientific imaging workflows needed a standard way to exchange image arrays and associated metadata for analysis, observation, and long-term archive use. FITS remains central in astronomy, astrophysics, and other specialist scientific-imaging domains where metadata and analysis compatibility are as important as the image itself. FITS is closely associated with NASA / IAU FITS ecosystem. FITS is usually selected for workflows that center on capture ingest, editing, web or print delivery. ## Typical Workflows - capture ingest - editing - web or print delivery ## Common Software - astronomy tools - NASA/IAU workflows - scientific imaging libraries ## Strengths - Strong fit for scientific metadata-rich imaging. - Long-lived standard in astronomy and related research. - Supports workflows where data interpretation matters more than casual viewing. ## Limitations - Not designed as a mainstream consumer image format. - Validation needs domain-aware tools, not just generic viewers. ## Related Formats - EXR - TIFF - DCM ## Interesting Context FITS became a durable scientific standard because observatories, spacecraft, and analysis tools needed a stable interchange format that outlived individual instruments and software stacks.
IMAGE
Krita Brush
gbr, gbrush
## Overview GBR matters because paint workflows need reusable bitmap brush tips with stable spacing and stamping behavior, which is a different problem from ordinary raster-image delivery. Artists needed a way to save brush-tip images together with the brush behavior expected by painting tools so those resources could be reused across sessions and projects. GBR remains relevant in GIMP-centered painting workflows and in other raster editors that import GIMP-style bitmap brush resources for compatibility. Krita Brush is closely associated with GIMP Project. Krita Brush is usually selected for workflows that center on capture ingest, editing, web or print delivery. ## Typical Workflows - capture ingest - editing - web or print delivery ## Common Software - GIMP - Krita - paint and texture authoring tools ## Strengths - Preserves reusable bitmap brush tips as authoring assets. - Simple fit for stamp-based painting and texture workflows. - Still interoperable enough to matter beyond GIMP itself. ## Limitations - Not a general-purpose image-delivery format. - Feature expectations vary across editors that import GBR brushes. - Brush behavior is narrower than what richer preset systems can encode. ## Related Formats - PAT - GIH - VBR - PNG ## Interesting Context GIMP's brush formats grew out of the need to preserve painting resources as reusable assets rather than flattening every stroke into ordinary image files.
IMAGE
GIF
gif
## Overview GIF remains culturally important because it combines simple raster delivery with a lightweight animation model that spread early across browsers, forums, chat clients, and meme culture long before modern web-video formats matured. Online services needed a compact raster interchange format for dial-up era graphics that could move reliably between different hardware and software environments. GIF is now most relevant as a compatibility-first graphics and short-loop animation format rather than the most efficient way to deliver photographic or motion content. GIF is closely associated with CompuServe legacy format with broad web/browser support. GIF is usually selected for workflows that center on capture ingest, editing, web or print delivery. ## Typical Workflows - capture ingest - editing - web or print delivery ## Common Software - Browsers - Photoshop - ImageMagick - chat and social apps ## Strengths - Broad support across browsers, messaging tools, and social platforms. - Simple animation support without needing a separate video player. - Predictable rendering for flat-color graphics and short looping visuals. ## Limitations - Its 256-color palette is a poor fit for photographic fidelity. - Animated GIFs are usually much larger than modern video alternatives. ## Related Formats - PNG - WEBP - MP4 ## Interesting Context CompuServe introduced GIF in the late 1980s, and the later GIF89a revision added capabilities such as transparency and simple animation that made the format much more versatile on the early web.
IMAGE
HDR
hdr
## Overview HDR-family image files matter because some imaging workflows need to preserve light values, exposure latitude, or rendering data that ordinary low-dynamic-range display formats cannot represent well. Rendering and imaging systems needed a file format that could store scene values and extended dynamic range instead of clipping everything to conventional display assumptions. HDR raster files still appear in rendering, lighting, environment maps, and technical imaging workflows. HDR is closely associated with HDR imaging and rendering ecosystem. HDR is usually selected for workflows that center on capture ingest, editing, web or print delivery. ## Typical Workflows - capture ingest - editing - web or print delivery ## Common Software - renderers - lighting tools - ImageMagick ## Strengths - Supports workflows where dynamic range matters more than consumer display compatibility. - Useful in rendering and lighting pipelines. ## Limitations - Not a mainstream end-user delivery format. - Needs workflow-aware viewing and validation. ## Related Formats - EXR - DPX - TIFF ## Interesting Context HDR raster formats became important in rendering and lighting workflows before consumer-facing HDR delivery stories matured in mainstream media formats.
IMAGE
HEIC
heic
## Overview HEIC matters because it became the most visible consumer-facing HEIF variant through Apple device adoption, bringing modern image-container efficiency into mainstream mobile photography workflows. Mobile devices needed more storage-efficient image handling without giving up richer metadata and modern photo features. HEIC is now strongly associated with phone-photo capture, mobile sharing friction, and cross-platform compatibility decisions between Apple devices and other software ecosystems. HEIC is closely associated with Apple ecosystem usage on top of MPEG HEIF/HEVC standards. HEIC is usually selected for workflows that center on capture ingest, editing, web or print delivery. ## Typical Workflows - capture ingest - editing - web or print delivery ## Common Software - Apple Photos - iOS and macOS camera workflows - cross-platform converters ## Strengths - Space-efficient in mobile photography workflows. - Tied to modern metadata-rich image handling. - Common in real consumer capture pipelines rather than only in theory. ## Limitations - Cross-platform compatibility remains less universal than JPEG. - Many users only notice HEIC when another system refuses it or converts it. ## Related Formats - HEIF - JPG - AVIF ## Interesting Context HEIC became widely recognized when Apple adopted HEIF-based image storage in its consumer ecosystem, turning a standards-driven container family into an everyday format users actually encountered.
IMAGE
HEIF
heif
## Overview HEIF matters because it is a flexible image container designed for modern imaging workflows, including still images, bursts, sequences, metadata, and computational-photography style packaging rather than just one flat bitmap payload. Newer imaging workflows needed a more efficient, feature-rich way to package still images, bursts, derived images, and related metadata than older single-image delivery formats allowed. HEIF is important in mobile photography and modern imaging pipelines where efficient storage, metadata, sequences, and derived-image workflows matter. HEIF is closely associated with MPEG / ISO Base Media File Format ecosystem. HEIF is usually selected for workflows that center on capture ingest, editing, web or print delivery. ## Typical Workflows - capture ingest - editing - web or print delivery ## Common Software - Apple Photos ecosystem - modern mobile imaging stacks - specialist imaging tools ## Strengths - Can package richer image relationships and metadata than older flat image formats. - Designed for modern photo and computational imaging use cases. - Supports both still images and image sequences. ## Limitations - Tooling and compatibility are not as universal as the oldest web raster formats. - Interoperability depends on both the container profile and the encoded image data inside it. ## Related Formats - HEIC - AVIF - JPG - PNG ## Interesting Context HEIF was developed by MPEG and built on the ISO Base Media File Format lineage, which helps explain why it feels more like a modern media container for images than a simple legacy bitmap file.
IMAGE
ICB
icb
## Overview ICB, VDA, and VST matter because early PC graphics and video-capture workflows often emitted board-specific filename variants for closely related Truevision raster data, so preservation and migration work still encounters them as distinct compatibility cases. Early graphics hardware and paint software needed board-native raster files for capture, paint, overlay, and interchange workflows in a still-fragmented PC graphics market. These extensions now matter mainly in preservation, migration, retro-computing, and graphics-archive cleanup where historically named Truevision assets still need to be opened or normalized. ICB is closely associated with Truevision (now Pinnacle Systems). ICB is usually selected for workflows that center on capture ingest, editing, web or print delivery. ## Typical Workflows - capture ingest - editing - web or print delivery ## Common Software - ImageMagick - legacy graphics tools - preservation workflows ## Strengths - Important for long-tail compatibility with historic Truevision-era assets. - Close family resemblance to TGA simplifies some migration paths. - Useful for preserving provenance from early video-graphics toolchains. ## Limitations - Weak modern software recognition compared with ordinary `.tga` files. - Public documentation is mostly historical or secondary. - Usually converted quickly into more recognizable raster formats once identified. ## Related Formats - TGA - BMP - PNG ## Interesting Context The Truevision line grew out of EPICenter-era PC graphics boards, and several board names ended up surviving as filename extensions even when the underlying raster structure stayed close to the wider TGA family.