Develop the RAW photograph in a compatible external RAW processor before handing a rendered copy to an AI image workflow. Decide exposure, white balance and important highlight detail while the sensor data is available. Keep the original RAW and its development settings; the uploaded JPEG or PNG is a new working copy, not a replacement negative.
Why the camera file needs a development decision
A camera RAW is not simply a larger JPEG. Adobe’s Camera Raw introduction explains that the processor interprets sensor data and preserves the original while storing development settings. A thumbnail from the camera or file browser is therefore not a reliable description of the image you have chosen to render.
Open the file in software that supports the camera model. Check whether the face, product label or bright dress contains useful detail before increasing contrast. Correct a color cast while comparing believable neutral objects, rather than making everything warmer because a preview looks gray. These choices create the source appearance against which later AI changes can be judged.
Make a clean rendered handoff
Keep a development master in an appropriate external format, then export a separate copy accepted by the current upload control. Adobe documents processed-image saving separately from RAW processing. A TIFF can be useful in your own editing archive even if the website currently requires another format. Check the actual control instead of assuming TIFF, DNG or every camera extension is supported.
Choose enough pixels for the intended composition. Avoid several rounds of JPEG opening and resaving before upload. Bake the intended orientation into the visible image and inspect the exported file outside the RAW application. If the subject becomes too dark or the colors shift at this stage, fix the rendered handoff before asking the AI to compensate.
Three files make the distinction easy to understand: the untouched camera original, an external development master and a supported upload copy. Your naming can be different, but the roles should remain clear. The AI result then becomes a fourth file with its own approval, rather than silently overwriting the developed source.
An invented portrait handoff
In a fictional example, Mara has a window-lit portrait named Mara-014.CR3. She saves the camera file unchanged, records her external development settings and exports Mara-014-developed-v1.jpg. The exposure adjustment makes the eye visible without clipping the white blouse. Only this rendered copy enters the selected workflow from Imagild Image Prompt.
Her creative brief asks for a quiet painted background while retaining the developed face and blouse. She compares the result against developed-v1, not against a darker camera thumbnail. If the result invents blouse texture, she rejects that version; she does not alter the RAW merely to make the generated image seem faithful. This is a planning example, not a reported generation test.
When to stop and return to development
Return to the RAW processor if the uploaded source has an avoidable overall exposure or color problem. A generative edit can create plausible detail, but that is different from revealing recorded detail. Also stop if the RAW application cannot interpret the file correctly: use the camera maker’s supported software or another verified compatible processor.
Does saving a RAW as PNG keep the RAW controls?
No. It creates rendered pixels. The original sensor data and development settings belong to the original workflow, so preserve them separately.
Should I export the largest possible file every time?
Use dimensions appropriate to the task and current upload limits. More pixels do not correct a poor development choice or make invented detail authentic.