{"id":2611,"date":"2026-08-08T01:50:57","date_gmt":"2026-08-07T22:50:57","guid":{"rendered":"https:\/\/picajet.com\/articles\/formats\/3fr\/"},"modified":"2026-08-08T03:47:20","modified_gmt":"2026-08-08T00:47:20","slug":"3fr","status":"publish","type":"format","link":"https:\/\/picajet.com\/articles\/formats\/3fr\/","title":{"rendered":"3FR"},"content":{"rendered":"<p class=\"wp-block-paragraph\">Hasselblad introduced 3FR in 2006 with the H2D, part of its H-system medium-format camera line, as the successor to earlier Hasselblad raw formats used with its digital backs. Like most manufacturer raw formats, it is built on a TIFF skeleton, but it is tuned specifically for Hasselblad&#8217;s medium-format sensors, storing unprocessed data at 16 bits per channel \u2014 a wider bit depth than most 35mm-format raw files, reflecting the greater dynamic range medium-format sensors typically capture.<\/p><p class=\"wp-block-paragraph\">Compression behavior has changed across Hasselblad&#8217;s camera generations: earlier bodies wrote 3FR with lossless compression to manage file size, while newer bodies more often save uncompressed 3FR, prioritizing simpler, more predictable file handling over storage efficiency \u2014 a reasonable trade-off for photographers whose entire workflow already assumes large medium-format file sizes.<\/p><p class=\"wp-block-paragraph\">For a DAM, 3FR sits in a moderate-risk category: Hasselblad is a long-established, currently active manufacturer with its own maintained software (Phocus), and mainstream tools like Adobe Camera Raw and Capture One support the format well. That said, it remains undocumented and proprietary, so converting to DNG for cross-team access and long-term archival is still good practice, particularly for studios and agencies where not every seat has access to Phocus or Capture One.<\/p>","protected":false},"excerpt":{"rendered":"<p>3FR is Hasselblad&#8217;s proprietary raw format for its medium-format camera systems, introduced in 2006 with the H2D and storing 16-bit-per-channel unprocessed sensor data.<\/p>\n","protected":false},"author":0,"featured_media":0,"template":"","meta":{"footnotes":"","faq":[{"question":"Does 3FR carry the same vendor-abandonment risk as formats like SRW or MOS?","answer":"No. Hasselblad remains an active manufacturer, so 3FR carries less immediate vendor-abandonment risk than several niche or discontinued formats, though it is still an undocumented proprietary format outside a small professional software ecosystem."},{"question":"What bit depth does 3FR capture at?","answer":"3FR captures at 16 bits per channel, matching the higher bit depth typical of Hasselblad's medium-format CCD and CMOS sensors rather than the 8-bit output of processed derivatives like JPEG. This wider tonal range preserves more highlight and shadow detail for later grading. For a DAM archive, it means the raw master retains substantially more recoverable information than any exported preview, which is one reason the original 3FR should stay the retained asset rather than being replaced by a rendered copy."},{"question":"Has 3FR's compression approach changed across Hasselblad camera generations?","answer":"Yes. Earlier Hasselblad bodies wrote 3FR with lossless compression, keeping files smaller without discarding any sensor data, while more recent cameras typically save uncompressed 3FR to simplify writing speed and decoding, at the cost of noticeably larger files. Neither approach affects image fidelity, since lossless compression never discards data. For a DAM, this means storage and bandwidth budgets should account for larger file sizes from newer camera bodies, even though quality and processing behavior remain effectively unchanged between generations."},{"question":"Which software gets closest to full-fidelity 3FR processing?","answer":"Phocus, Hasselblad's own free tethering and processing application, gets closest to full-fidelity results because it applies the company's camera-specific color calibration and lens correction profiles directly. Third-party tools such as Adobe Camera Raw, Capture One, darktable, and RawTherapee (via libraw) can open 3FR files and are widely used in professional workflows, but they reconstruct color and lens behavior through reverse-engineered profiles rather than Hasselblad's own data. A DAM archive should keep Phocus available for any fidelity-critical review, even if broader tools generate day-to-day previews."},{"question":"Should a DAM convert 3FR masters to DNG?","answer":"Yes. Converting to DNG gives a DAM archive a widely supported, self-documenting format that most cataloging, preview-generation, and search tools can read without needing libraw or Hasselblad-specific decoders. The original 3FR should still be retained as the archival master, since it carries the full data Phocus was designed to interpret, including camera-specific calibration Phocus applies natively. Keeping both means the DNG serves everyday browsing and interoperability, while the original 3FR stays available for photographers who still process files in Phocus."},{"question":"When was 3FR introduced?","answer":"3FR was introduced in 2006 alongside the Hasselblad H2D, one of Hasselblad's early integrated digital medium-format camera bodies. The format has remained in use across the company's subsequent digital lines since then, meaning a DAM archive built from a longstanding Hasselblad workflow may contain 3FR files spanning close to two decades of camera generations, with the compression differences noted elsewhere in this FAQ reflecting that span."},{"question":"Is there a published specification for 3FR?","answer":"No, Hasselblad has not published a formal specification for 3FR. Third-party support instead comes from reverse-engineered decoding, most notably through the open-source libraw library, which underlies raw support in tools like darktable and RawTherapee, alongside Adobe Camera Raw and Capture One maintaining their own interpretations. For a DAM, this unofficial status is the main reason to treat 3FR masters as read primarily through Phocus or through libraw-based tools, and to generate a standards-based derivative like DNG or TIFF for long-term interoperability rather than relying on the raw format alone."},{"question":"What structural family is 3FR based on?","answer":"3FR belongs to the broad family of TIFF-based raw formats, the same structural lineage used by many other vendor raw formats. Its container wraps EXIF metadata and unprocessed medium-format sensor data inside standard TIFF tags and structure, rather than inventing an entirely proprietary file layout. Practically, this means generic TIFF-aware tools can often read the embedded metadata and thumbnail even without being able to decode the actual sensor data, which is useful for a DAM that needs to extract searchable metadata from 3FR files it cannot fully render."}],"checked_date":"2026-08-11","sources":[{"statement":"Hasselblad introduced the 3FR format with the release of the Hasselblad H2D camera in 2006","source_name":"CleverFiles, 3FR file format guide","url":"https:\/\/www.cleverfiles.com\/howto\/recover-deleted-3fr.html","checked":"2026-08-07"},{"statement":"The 3FR format is based on TIFF, storing unprocessed sensor data at 16 bits per channel with EXIF metadata; older-generation files use lossless compression while newer files are typically uncompressed","source_name":"Just Solve the File Format Problem (Archive Team wiki), Hasselblad 3FR","url":"http:\/\/fileformats.archiveteam.org\/wiki\/Hasselblad_3FR","checked":"2026-08-07"},{"statement":"3FR files can be opened with Hasselblad's Phocus software, viewers, and converters","source_name":"FileInfo.com, 3FR file description","url":"https:\/\/fileinfo.com\/extension\/3fr","checked":"2026-08-07"}],"kicker":"","fact_checker":0,"reading_time":0,"revisions":[],"seo_title":"3FR file: Hasselblad raw format, how to open and convert","seo_description":"","noindex":false,"ext":"3fr","full_name":"Hasselblad 3F RAW","vendor_name":"Hasselblad","introduced":"2006, with the Hasselblad H2D","container_notes":"3FR is a TIFF-based container holding unprocessed medium-format sensor data at 16 bits per channel, along with EXIF metadata. Older Hasselblad generations compressed 3FR losslessly; current bodies typically write it uncompressed, trading file size for simplicity and predictable read performance. There is no public specification, and full-fidelity processing is closest to Hasselblad's own Phocus software, which understands the company's specific color and lens correction profiles.","open_with":[{"platform":"Windows \/ macOS","how":"Phocus, Hasselblad's own free tethering and raw-processing software, native and tuned for the sensor and lens profiles"},{"platform":"Windows \/ macOS","how":"Adobe Camera Raw \/ Lightroom Classic, with standard 3FR camera support"},{"platform":"Professional workflows","how":"Capture One, widely used for medium-format tethered shooting"},{"platform":"Cross-platform, open source","how":"darktable or RawTherapee, both decoding 3FR via libraw"}],"archive_advice":"Hasselblad remains an active manufacturer, so 3FR carries less immediate vendor-abandonment risk than several niche or discontinued formats in this list, but it is still an undocumented proprietary format outside a small professional software ecosystem. Convert 3FR to DNG for broad interoperability and search\/preview generation in a DAM, while retaining the original for teams that continue working in Phocus.","related":[2604,2602,2603,2610,2594,2607],"tool_link":""},"silo":[23],"class_list":["post-2611","format","type-format","status-publish","hentry","silo-formats"],"_links":{"self":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/format\/2611","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/format"}],"about":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/types\/format"}],"version-history":[{"count":3,"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/format\/2611\/revisions"}],"predecessor-version":[{"id":3669,"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/format\/2611\/revisions\/3669"}],"wp:attachment":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/media?parent=2611"}],"wp:term":[{"taxonomy":"silo","embeddable":true,"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/silo?post=2611"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}