From RAW Development to Photoshop, Managing Edits and Image Versions

Why Photographers Love Their Tools · An editorial collection from Zippi Technologies. We develop Lightbox Pro; these are educational explanations, not independent product rankings or measured competitor tests.

Begin with the revision you need to preserve

A portrait arrives at Photoshop after several decisions have already been made: which exposure, which interpretation, which crop direction and which local changes are authorized. If those decisions are not explicit, the retoucher may create a beautiful document that is difficult to return to the rest of the job.

This guide follows an invented 6,000 by 4,000-pixel portrait. The photographer wants a temporary skin distraction removed, a small background repair and separate print and web deliveries. The master must remain revisable. The dimensions and requests are illustrative; they are not a client case or a specification for every portrait.

Write the brief against an identified source and working rendering. State what should change, what should remain and which later revision must be possible. “Remove the temporary mark; retain natural texture; keep the full composition for future crops” gives a more useful boundary than “retouch this final.”

The existing RAW and retouching series chapter explains the broader division of labor. This guide concentrates on the actual handoff settings, a working file’s responsibilities and the return path.

Use three roles: source, master and output

The source is the camera capture with the relevant development record. The master is the editable finishing document. An output is a destination-specific rendition derived from an accepted stage. A single exposure can therefore legitimately produce several files without those files being redundant.

Keep the original RAW available. A rendered TIFF or PSD contains an interpretation of that source, not a new sensor capture. If the photographer later changes the RAW interpretation, the retoucher may need to assess how the change affects local work. The earlier raster file cannot magically recover every upstream processing choice.

For the example, identify the working master as revision 01 and keep web and print outputs outside the master’s role. A client’s selected JPEG is not automatically the editable master merely because it was the file most recently opened.

The version-management guide expands the relationship record. Here, write just enough to prevent ambiguity: source identifier, RAW interpretation, master revision, output purpose and approval state.

Choose TIFF or PSD for the job’s required editability

TIFF and PSD can support high-quality working images, but the extension alone does not prove a particular document retains layers or every required feature. PSD is a natural Photoshop working-document choice; TIFF can also be appropriate where the agreed application workflow preserves what the recipient needs.

A JPEG is useful for many delivery and preview roles, but it is not a layered editing master. Repeatedly using small JPEG derivatives as the next stage’s source can discard flexibility that the original processing and finishing work were meant to retain.

Scroll within the table to read all columns.

If a document approaches an application or format limit, review the current supported route, including large-document options where relevant. Do not flatten the only master or split dependencies casually just to make a file save. Agree a complete recoverable representation first.

Bit depth provides working precision, not a quality verdict

Adobe’s external-editing preferences let the operator choose working format, color space and bit depth. A 16-bit-per-channel SDR working file can provide more numerical precision for substantial adjustments than an 8-bit one. It does not establish correct exposure, pleasing color or successful retouching.

For this portrait, use a supported high-precision working route when the intended corrections justify it and every required tool supports it. Check the actual saved document mode after the handoff. A preset label is not evidence that the receiving file has the expected precision.

Keep precision and source quality separate. Converting an already limited image to a larger numerical container does not restore information previously discarded. Likewise, a high-precision master can still contain an unwanted crop, clipped interpretation or mistaken layer state.

Reopen a representative master and inspect the gradients and difficult transitions relevant to the job. The point is to preserve the room required for the next edit, then verify the photographic result. Do not choose a larger format merely because larger sounds more professional.

Agree the working profile and convert deliberately

A color profile helps describe how numerical color values should be interpreted. An external-editing preset and the receiving editor’s color settings need a coherent relationship. A profile warning is information to understand, not an interruption to dismiss automatically.

Agree the working space appropriate to the editor and destination, then verify the saved master’s embedded profile. Distinguish assigning an interpretation from converting colors to a different space. These actions serve different purposes and can produce different appearances.

For the example, record the working profile in the job note, preserve it in the master and prepare each delivery through the agreed conversion. A client needing a web rendition should receive an appropriate output rather than an unexplained working document that happens to open on the photographer’s display.

When appearance differs across applications, compare the same saved file under known color-management conditions. Do not immediately add a compensating edit to one copy. First identify whether the difference comes from the file, profile handling, viewing conditions or a genuinely different rendering.

Send the accepted rendering, not an ambiguous open command

In Lightroom Classic, review the configured Photoshop external-editing path and the actual choices presented for the selected file. A RAW source and a previously rendered TIFF do not necessarily present the same handoff behavior. Preserve the original and verify the newly saved derivative in the catalog afterward.

For Capture One, the official external-editor reference distinguishes using Edit With to exchange an adjusted RAW interpretation from reopening a processed file with Open With. Opening a RAW source directly in another processor is not the same operation as sending the accepted Capture One rendering.

Before the full job, send one test portrait and check dimensions, orientation, profile and appearance. Save the working master, return to the catalog and confirm its source relationship. A completed launch of Photoshop only proves the application opened; the accepted handoff includes the correct image and a usable return.

If the result differs from the expected rendering, stop on the small test. Do not make the retoucher compensate by eye across an entire job while the upstream contract remains unclear. Resolve which pixels and settings were intended to cross the boundary.

Work the portrait as a controlled finishing document

Keep an unaltered reference within the private project or otherwise accessible through the approved workflow. Separate the local repair from the global tonal treatment so each can be reviewed for its own purpose. Use names that explain the decisions rather than relying on a colleague to infer them from thumbnails.

The portrait’s temporary mark is removed, but skin texture remains part of the person’s appearance. Compare the repaired area with surrounding skin and inspect the face as a whole. Then review the background repair at the intended crop. A local edit can be technically smooth and still alter the photograph in an unwanted way.

Save a working revision before a substantial change to the brief. If the client requests a more restrained treatment, the retoucher should be able to return to a known accepted state rather than reconstructing it from memory.

The diagram describes responsibilities. It does not claim that any named application automatically creates a complete version-management graph.

Work the pixel arithmetic before setting a print number

Adobe distinguishes pixel dimensions, print density and resampling. Changing a resolution label without resampling does not add pixels. That distinction prevents the common mistake of believing that typing a larger ppi value can recover detail from a small delivery file.

The example 6,000 by 4,000-pixel portrait contains 24 million pixels. At 300 pixels per inch, the uncropped dimensions correspond arithmetically to 20 by approximately 13.33 inches. These are calculations, not a universal print recommendation. A printer may specify another density, crop or preparation requirement.

A 4:5 crop from that landscape source might retain 3,200 by 4,000 pixels, depending on the chosen orientation and content. At 300 ppi that is approximately 10.67 by 13.33 inches. The crop has changed the available pixels; changing the ppi label afterward cannot recover the discarded composition.

For web use, prepare the pixel dimensions the actual destination needs. Avoid repeatedly resizing an earlier small output. Return to the accepted master, create a new rendition and inspect the result, including any output sharpening or compression chosen for that destination.

Estimate storage without mistaking an estimate for a file size

A simple uncompressed RGB estimate for the full portrait at 16 bits per channel is 6,000 × 4,000 × 3 × 2 bytes: 144,000,000 bytes, or about 137.3 MiB. This counts one RGB pixel array. It excludes layers, masks, previews, metadata, compression and application-specific storage.

A layered document can therefore occupy substantially more or less disk space than a casual estimate suggests, depending on its contents and compression. Measure actual saved files when planning a real job. Do not publish the pixel-array calculation as a prediction of Photoshop’s final document size.

Include working space and independent recovery copies in the plan. Keeping a master plus multiple outputs is not simply “waste” if each serves a required role. At the same time, an undocumented accumulation of obsolete temporary files can make it harder to identify the material that genuinely needs preservation.

Use a deliberate cleanup review after acceptance, with the job’s source/master/output record available. Never delete a large file solely because a smaller JPEG looks similar. The larger file may contain precisely the editability needed for the next request.

Verify the return and the revision path

After saving the master, reopen it through the intended catalog or file workflow. Confirm the exact location and whether the catalog has recognized the new file. A file saved into a different folder or under an unexpected name may need an explicit supported import or synchronization step.

Then rehearse a real revision. Ask for a small change to the local repair while retaining the accepted crop and color treatment. Open the master, make the change, save a new identified revision and generate fresh outputs. Check that the previous delivery record remains identifiable.

If the master uses linked material, package or preserve that material according to the agreed workflow. Adobe documents linked Smart Objects as external dependencies. A copied document with missing links is not a complete handoff merely because its composite preview remains visible.

Record the revision’s approval separately from the earlier request. A person asking for a change has not necessarily approved the result before seeing it. Keep the review tied to a named master/output revision.

Back up the dependency, not only the attractive file

Preserve the source, processing record, editable master, required linked material and released outputs under the assignment’s recovery policy. These records answer different future questions: what was captured, how it was interpreted, how it was finished and what was sent.

Test the package on a separate copy. Reopen the master, resolve its expected sources and reproduce one representative output. Compare it with the accepted result under an appropriate review method. A successful file copy is necessary but does not establish complete interpretability.

Keep an exception note for anything that cannot currently be reproduced. An unavailable font, missing external object or unsupported old processing version should remain visible rather than being concealed by a final JPEG that still happens to look correct.

The backup strategy guide covers broader recovery planning. The critical handoff rule is simple: do not discard the original or only editable master because a client has approved a delivery derivative.

Follow a late portrait correction through the files

The client approves master r02, then notices a small distraction in the wider print crop. The web version is already published and uses a tighter crop that does not show that area. Identify the requested change against the print output before deciding which files must be revised.

Open the accepted editable master, confirm its source relationship and create an identified working revision. Repair the newly relevant area without rebuilding unrelated accepted work. Inspect the full composition and the print crop, then save master r03 with the required editability intact.

Prepare the new print rendition from r03 and record which earlier output it replaces. Do not silently overwrite the only evidence of the previous delivered print file. The job record should show the request, the revised master and the new release.

Now assess the web branch. If the repair is outside its crop and no other visible change was made, the existing web output may remain appropriate. That is a scoped decision, not an automatic rule. Inspect the actual output before deciding that it is unaffected.

If the client also asks for a brighter face, that changes a common photographic decision and may affect both branches. Return to the appropriate editable level, assess the local repair under the new treatment and regenerate every output whose accepted appearance changes. The dependency record determines the scope.

Keep color and size settings tied to each destination. A new print file should not inherit a small web preset merely because the web output was the last export performed. Recheck the selected preset, resulting dimensions and embedded profile before sending.

Finally reopen the new master from a copied project location and locate both released print revisions from the ledger. Another operator should be able to distinguish the current delivery from historical evidence without relying on file timestamps or a suffix such as “really-final.”

This exercise exposes a common source of hidden labor: the edit itself may be modest, but identifying its dependencies and updating the correct releases requires care. A well-defined source/master/output relationship makes that care bounded and repeatable rather than forcing the photographer to inspect every similar file again.

Lightbox Pro’s current boundary

The reviewed Lightbox Pro build 0.1.2 (71) contains native corrected export for JPEG, TIFF and flattened PSD, with actual profile conversion, supported precision options and guarded publication. Current source also uses sensor-based RAW development and a shared preview/output processing architecture. These are implemented development capabilities, not merely planned buttons.

However, a flattened PSD does not preserve Photoshop layers, and photographic RAW acceptance remains open. Build 71 adds source-pixel Edit zoom and panning, with asynchronous source-detail inspection that follows unapplied edits; initial detail loading can still take time. The documented subtle wedding-highlight texture issue remains unaccepted, preventing a claim of mature RAW processing parity. Advanced portrait retouching and complete hosted delivery remain future goals.

A useful integration direction is to retain the source/master/output relationship around external finishing. Until the required editing depth is implemented and accepted, a clear Photoshop handoff remains a professional strength of the workflow rather than something to conceal.

Official references

1. Adobe: external editing preferences
2. Capture One: external-editor commands
3. Adobe: image dimensions and resampling
4. Adobe: linked Smart Object dependencies
5. Adobe: saving Photoshop files

Product documentation checked 22 October 2026. Examples and worksheets are original teaching scenarios. Confirm the current version, camera support and terms before adopting a workflow.