Photo retouching PSD to JPEG: finish exposure, noise, and skin work in 16-bit masters—JPEG is for distribution previews, not rescue passes
Portrait and product shots often stack curves, LUTs, and local brushes; expecting the online PSD-to-JPEG hop to “fix” issues rarely works because 8-bit output quantizes highlights you barely recovered. `photo-psd-jpg` fits when retouching is approved and you only need a compressed client or merchandising preview while the layered PSD remains canonical. Finish denoise, skin neutrality, and highlight protection before flattening; the online step should only encode agreed dimensions and quality so “dirty skin” feedback routes back to the PSD, not to irreversible JPEG tweaks.
Comment utiliser
- Ensure Camera Raw/PS steps leave no clipped channels or posterization, complete local work in 16-bit where needed, then convert to 8-bit for handoff; the ticket should say “no further color work on JPEG” to keep accountability clean.
- Review the JPEG on a calibrated display for neutral skin axis, hair highlights, and fabric texture, then sanity-check a phone screen; if desktop looks fine but mobile shifts, fix document profile and viewing assumptions instead of slamming saturation.
- Name files with scene tags like LOOKBOOK_WEB distinct from future PRINT_MASTER drops; keep PSD and lossless TIFF internally so print reruns never start from a JPEG.
PSD to JPG (photo) FAQ
Portrait skin shifts green or magenta—what do we check first?
Start with a profiled monitor and a document profile that matches delivery intent, verify every adjustment layer is active before merge, and watch for forgotten hidden adjustments; if the viewing chain mimics a popular phone browser, soft-proof or export phone swatches instead of judging everything on an unmanaged laptop panel alone.
Lifted shadows get noisy—can online export fix it?
Finish denoise and local exposure in PSD first; online export is for distribution, not rescue.
Blown highlights—can JPEG bring detail back?
No if pixels clip; recover highlights in source or use 16-bit intermediates on desktop before JPEG.
Photo needs print and web—how do we split JPEG strategy?
Send print through vendor-approved CMYK or high-bit TIFF/PSD packages with desktop soft-proofing; publish web and social JPEGs as a separate sRGB set with explicit long-edge and quality—never reuse one filename for both worlds. If the business insists on “one asset everywhere,” at least document each use and its limits or color arguments become inevitable.
Batch presets before JPEG—how do we stop WB drift?
Lock preset versions, daily sample checks, tag outliers instead of spreading bad presets.