A practical checklist before exporting a RAW photo

Distinguish the source from the deliverable

A camera RAW file contains sensor-derived information that an editor interprets into a visible image. It gives more room to make exposure and white-balance choices than a finished JPEG in many workflows, but it needs development before most recipients can use it. A JPG export is a rendered delivery copy, not the same kind of working material.

Give the original and export different names and locations. Keep any sidecar file or editing catalog that stores your adjustments, because an exported JPEG does not carry every slider setting as an editable operation. If the recipient asks only to view the photograph, send the rendered file. If they need to edit from the capture, agree on the source workflow instead of assuming the JPG is equivalent.

• Preserve the camera original untouched.
• Keep adjustment records when later revisions matter.

Set exposure and color deliberately

Before export, inspect the brightest areas that should retain detail and the shadows that should remain understandable. RAW editing can allow meaningful changes to those areas, but no setting can reconstruct scene information the camera never recorded. Avoid pushing controls until smooth gradients become harsh or noise becomes distracting just because a preview looks dramatic.

White balance is also a decision made when the raw data is rendered. Compare a neutral object if one is present, but do not force every scene to the same color temperature. Skin, white packaging, and known brand colors deserve extra attention. Review on a reasonably calibrated display when color precision matters, and accept that other displays may differ.

• Check highlights and shadows separately.
• Revisit skin and neutral areas after changing white balance.

Choose output settings for the destination

The intended use determines format, dimensions, and file size. A JPEG is broadly useful for photographic sharing and uses lossy compression. A lossless format may be preferable if a recipient will continue pixel editing, but it can be larger. Confirm what the receiving app, print service, or website accepts rather than exporting one giant file for every purpose.

Set pixel dimensions intentionally. A web thumbnail does not need the same pixel count as a print submission, and enlarging an export cannot create genuine captured detail. If a service supplies a maximum size, make a dedicated copy for it. Use descriptive filenames so that a small web export is not mistaken for the full-resolution version.

• Read the destination's dimensions and format rules.
• Make separate web and high-resolution copies when needed.

Inspect the rendered file, not just the editor

An editor's RAW preview is not the final delivery file. Open the exported image in another viewer and compare framing, orientation, color, and important detail. Inspect at the display size and at full resolution. Small text in a photographed sign, hair, foliage, and high-contrast edges reveal oversharpening or compression changes more readily than empty areas.

If a platform later re-encodes the upload, inspect that delivered version too. A local export can be correct while the receiving site crops it or changes its display. Make one controlled change at a time when troubleshooting, so you can tell whether the problem came from export settings or from the destination.

• Reopen the actual output file before sharing.
• Check the delivered platform version where possible.

Keep a reversible archive and check privacy

Archive the RAW, adjustment record, and approved export as separate items. A new audience may need a different crop or color treatment later, and returning to the source is more reliable than repeatedly recompressing a prior delivery JPG. If the export fails a review, change the development settings and make a fresh copy.

Before handing off the file, inspect details that should not be visible in the photograph and review metadata when relevant. A RAW-to-JPG conversion is not automatically a privacy-cleaning process. Check capture dates, device information, and any other data required or prohibited by the destination, then verify the actual delivered file. The goal is a usable image with a recoverable source.

• Store source, edits, and export distinctly.
• Review visible content and file information before publication.

Use a repeatable export check for a photo set

When exporting several RAW photographs, choose one frame with bright highlights, deep shadows, skin or another familiar color, and fine texture. Apply your intended settings and inspect its rendered output before exporting the whole set. This sample can reveal clipping, an unsuitable crop, or a file-size surprise early. It does not guarantee that every exposure in the set needs identical adjustments, so still inspect outliers.

Keep the export settings or a short note with the project: destination, pixel size, format, and quality choice. If someone requests a different crop later, you can return to the source and explain which delivery copy was approved. Avoid overwriting a previously accepted export with a differently processed file under the same name.

A final pass should compare at least one image on the destination platform, if possible. If it looks different there, work backward from the delivered version to the local export and then to the RAW preview. This sequence avoids changing RAW adjustments to compensate for a display or upload issue that happened after export.

• Test a varied sample before exporting a batch.
• Record the settings used for approved delivery files.