RAW vs JPEG vs TIFF vs HEIC: Which Format Should Photographers Use?

Choose the role before choosing the extension

A camera file, an editable working master and a delivery JPEG are different products of the same photographic job. Asking which format is “best” without naming the role is like asking which lens is best without naming the subject. The useful choice preserves the information needed for the next decision while meeting the recipient’s actual requirements.

This guide separates capture, working representation and delivery. It focuses on RAW, ordinary photographic JPEG, TIFF and HEIF/HEIC. The examples are planning exercises, not Lightbox Pro compatibility tests. A file extension does not establish a codec, bit depth, profile, camera support or successful processing path by itself.

Capture sourceKeep the camera’s original recording and its context

Working interpretationRetain editable decisions or an appropriate master

Destination fileRender for the agreed recipient, dimensions and color handling

For a hypothetical portrait commission, the camera source might be RAW, the retoucher’s working document a layered master, the designer’s placed image a TIFF and the client download a JPEG. That is not redundant simply because each file shows the same person. Each serves a different task. Record those roles so an assistant does not delete the only editable source as an apparent duplicate.

A practical format map

Scroll across for the format comparison.

Do not read the table as a quality ranking. A well-prepared delivery JPEG can be more appropriate for a lab than an untagged TIFF. A large TIFF made from a small compressed source does not recreate the missing capture information. A RAW file the recipient cannot interpret is not a useful final delivery merely because it contains camera-source data.

RAW is a family of camera recordings, not one universal file

Canon’s EOS R7 manual describes RAW and C-RAW as sensor-source recordings that can be processed into JPEG or HEIF, while retaining the RAW source. It also warns that software compatibility depends on the camera and application version. Treat that as a model-specific example, not a guarantee for all files with a familiar suffix.

A RAW preview and a RAW development result need not be the same interpretation. A viewer may display a camera-generated representation or a system-provided rendering. Your development application may apply different defaults, color handling and adjustments. A pleasing thumbnail therefore does not establish the result of another processor, and a dull initial rendering does not establish that the original data are defective.

RAW does not mean uncompressed. Nikon’s Z8 specifications list 14-bit NEF and multiple compression choices. Sony’s ILCE-7CR RAW recording options distinguish uncompressed, lossless-compressed and compressed recording, with size qualifications. Read the actual camera manual before treating two RAW modes as interchangeable.

Keep a small representative camera test set. Include an ordinary exposure, a difficult highlight, a rotated frame and any paired-file mode you use. Confirm that the intended processor opens the actual source, renders meaningful detail, retains adjustments and produces the needed output. A successful preview is only one stage of this test.

Retain the camera source when future interpretation matters. If you also create a rendered master, identify which processor and settings produced it. The rendered file preserves that appearance; the camera source preserves different possibilities. For the sequence of ingest, selection and processing handoffs, read the RAW workflow guide.

JPEG is a useful result, not a disposable inferior format

The ordinary photographic JPEG workflow trades some image information for practical file size and compatibility. Adobe’s JPEG save documentation describes its flattened 8-bit output and quality settings. Higher quality generally produces a larger file; the application’s number is not a universal quality scale shared by every encoder.

Copying a JPEG byte-for-byte does not repeatedly compress it. Opening it for viewing does not necessarily recompress it either. The relevant operation is decoding and encoding a new lossy result. Avoid a chain where each revision starts from the previous small export. Return to the retained working source when changing a delivery’s size, crop or treatment.

Inspect the resulting file at the intended use. Strong compression can affect fine patterns, edge transitions and smooth areas differently. A tiny screen preview may hide problems that become apparent in a larger layout. Conversely, a very large file is not proof of useful additional detail; dimensions, source quality and encoding all matter.

“JPEG” also names a broader standards family. The JPEG committee’s overview includes modes beyond the familiar baseline photographic workflow. This guide’s ordinary-JPEG advice should not be generalized to JPEG 2000, JPEG XL, JPEG XT or every lossless mode. Confirm what a particular application actually exports and what the recipient accepts.

Use JPEG confidently when it meets the destination’s requirements, while retaining the source and editable master separately. Check whether the recipient expects a profile, particular dimensions and a particular metadata policy. Do not assume a social-sharing copy is suitable for a full-page album placement simply because both end in .jpg.

TIFF describes a flexible container, not a guaranteed master quality

The Library of Congress TIFF description explains a tag-based raster wrapper with multiple encodings and color representations. A TIFF can therefore require more inspection than its extension suggests. Record its dimensions, precision, profile, compression and any application-specific components important to the job.

Adobe’s TIFF save options include uncompressed, lossless LZW/ZIP and JPEG-compressed choices, subject to format limits. A TIFF is not automatically lossless. Layers, transparency or multipage content also require support in the actual receiving application; merely recognizing the file does not prove every component will be retained.

For an illustrative retouch-to-layout exchange, agree on a rendered TIFF with a named profile and a supported precision. Preserve the retoucher’s editable document separately if later changes must revisit layers or masks. Ask the designer to place and inspect the test image before preparing the whole job.

A higher-precision TIFF can be useful for further tonal work, but converting an already reduced image to a larger container does not reverse earlier losses. Nor does saving a TIFF guarantee future readability without a tested backup and reader. Keep the format choice connected to a real preservation or production requirement, not just file size.

HEIF and HEIC need a compatibility and transfer check

Apple describes HEIF as a container for images and image sequences that can use HEVC encoding. HEIC is commonly encountered in that family; Canon’s example above uses .HIF. Container, compression technology and extension are related concepts, not interchangeable guarantees.

Apple’s HEIF media guidance describes supported device workflows and automatic conversion to a more compatible format during some sharing or import paths. “I sent the original” should therefore be checked against the file actually received. An export, messaging service or device setting can change the packet.

For a mixed phone-and-camera job, keep the received source before normalizing delivery copies. Note whether the image is intended for an HDR or SDR presentation, and test it in the actual output application. A color or brightness difference may concern interpretation rather than a missing photograph. Do not fix the difference by arbitrarily assigning a new profile or repeatedly converting until one screen looks pleasing.

If a lab or layout tool does not accept the source variant, create an agreed derivative with a validated conversion tool. Open it independently and confirm orientation, crop, appearance and metadata. Retain the HEIF source alongside the job record; a JPEG derivative can serve compatibility without becoming the only surviving capture.

Separate pixels, precision, profiles and compression

These four properties are often conflated. Pixel dimensions describe the width and height of the sampled image. Bit depth describes available numerical precision for stored samples. A color profile helps interpret color values. Compression controls how the image information is encoded. Increasing one property does not automatically repair a deficiency in another.

In an original worked example, a 6000 × 4000 image cropped to 4000 × 4000 has fewer source pixels available, regardless of whether it is saved as JPEG or TIFF. At a hypothetical 300 pixels per inch, that square supplies about 13.3 inches on each side without adding pixels. This is arithmetic, not a recommended print size or a quality certification. The lab’s process, viewing distance and image content still matter.

Eight bits provide 256 possible values per channel; more storage precision can help avoid coarse transitions during substantial processing when suitable source information is available. Adobe’s bit-depth documentation distinguishes these workflows. More bits alone do not establish greater captured dynamic range, better focus or a wider color gamut.

Profile assignment and profile conversion are different. Adobe explains that assignment changes interpretation, whereas conversion transforms values toward a destination appearance. An untagged or wrongly tagged large TIFF can produce a less reliable handoff than a correctly prepared JPEG. Preserve the working master before destination conversion.

Choose by destination: three concrete scenarios

A wedding needs editing latitude and compatible client downloads

Retain the camera source and its editing instructions. Produce client derivatives from the approved edit, with agreed dimensions and metadata. Keep the photographer’s editing selection distinct from delivered files and client print choices. A RAW-plus-JPEG camera mode creates associated representations, not permission to delete one without understanding the camera and studio workflow.

A designer needs a retouched photograph for an album

Ask for the supplier’s current template and image requirements first. Agree on a rendered input that the layout application handles correctly, while retaining the editable retouch master. Inspect the placed image at its actual crop and effective resolution. The deliverable may be JPEG, TIFF or another specified format; do not invent one universal production rule.

An archive mixes phone images, older RAW and finished TIFFs

Inventory before converting. Preserve the original source set and identify software needed for important interpretations. Test representative variants, including the awkward ones. Create access copies where useful, but document conversions and preserve the relationship to their sources. A blanket “convert everything to TIFF” operation can enlarge storage while failing to retain application decisions or original camera possibilities.

For each scenario, put the role in the folder or job note: capture, editable master, review, delivery or production. Keep the naming system small enough that another person can follow it. See the library organization guide and the album production workflow.

Preserve the relationship between representations

For an invented example, Job-042_Frame-018.CR3, a working document and Job-042_Frame-018_Print-v2.jpg should remain traceable to one photographic source. The filename is a convenient clue, not proof that the files match. Record the source identity and the treatment that produced the output. Check that a newly exported crop has not inherited the name of a different frame. When camera counters repeat across cards or bodies, establish unambiguous identities before derivatives multiply. This small discipline makes later format conversion and replacement requests much easier to audit.

A format acceptance test before the whole job

1. Choose representative originals. Include the exact camera mode or HEIF variant, a rotated image, an important color and any transparency or layers required.
2. Record the source properties. Note dimensions, format, profile, associated instructions and application versions. Use separate backed-up copies.
3. Run the actual route. Import, view, edit if required, export and transfer through the service the recipient will use.
4. Inspect the received file. Check dimensions, orientation, crop, appearance, metadata and any expected editability. Do not stop at the sender’s preview.
5. Keep the result and decision. Retain source, working record and approved derivative with a short note of what passed and what remains unsupported.

If the file fails to open, check the exact codec/camera mode and reader version. If it opens with the wrong appearance, inspect rendering defaults, profiles and HDR/SDR handling. If it is too small for the placement, find the larger source rather than merely changing a resolution field. If edits are missing, look for the associated catalog or sidecar and confirm the reader supports the instructions.

Apply those distinctions to Lightbox Pro

Reviewed Lightbox Pro build 0.1.2 (60) provides local cataloging, manual culling, Light Table and Loupe with explicit detail distinctions. Its RGB preview editing includes Crop, Light brightness/contrast, Levels, Color Balance and Duotone. Those controls do not constitute an accepted app-controlled RAW sensor processor. The original RGB preview histogram is not a live adjusted or sensor histogram.

True RAW development and completed protected full-source rendered export remain unfinished. Internal full-source preparation for single-image JPEG/TIFF/PNG does not establish a finished public export command, broad TIFF-variant support or universal HEIC/camera compatibility. File-copy handoff and rendered export are separate operations.

Evaluate the formats and source paths you actually use. For critical focus, distinguish verified source detail from system RAW detail-unverified, an editing preview or reduced offline pixels. Continue with the sharpness inspection guide and the editable-source workflow before treating a convenient preview as the whole photographic asset.