Assets & tasks / PRACTICAL ANSWER
Why Does RawTherapee Reopen My Product RAW With an Older Edit?
RawTherapee can store processing profiles beside RAW files, in a central cache or in both locations. If the two versions disagree, the configured profile-handling behavior matters. A newer-looking file or a successfully copied RAW does not by itself establish which processing settings RawTherapee will load.
Find the two possible edit records
RawTherapee stores processing settings in PP3 sidecar files. These are text-based instructions describing how the application should develop an image; they are not edited image pixels.
RawPedia documents storage beside the input photograph and in a central cache. For example, an image named mug.raw can have a neighboring mug.raw.pp3. Depending on Preferences, a cache entry may also exist.
When a RAW is moved to another computer, the image-adjacent PP3 can travel with it. A central cache does not automatically become part of that transfer. Conversely, an existing cache on the receiving computer may contain an older treatment for an image already processed there.
Start by locating the RAW, its neighboring PP3 and the relevant cache configuration. Record file identities and modification times, but do not assume the newest timestamp identifies the approved treatment.
Inspect configured precedence before changing files
RawPedia describes preferences controlling profile storage and which profile takes precedence when both image-adjacent and cached versions exist and differ.
Open the actual RawTherapee preferences and identify the configured behavior. Compare the two processing-profile contents or deliberately render controlled copies using the respective profiles.
If the image-adjacent file is approved but the cache version is loaded, correct the selection or preference deliberately. If the cache contains the approved settings and the sidecar is stale, preserve the approved cache treatment before changing precedence.
Do not delete the cache or overwrite every PP3 as a first diagnostic step. That can destroy useful edit history or make it harder to establish which version produced a previous delivery.
Also record the RawTherapee version. RawPedia notes that processing-profile compatibility can change across application versions, so identical settings do not guarantee perfectly identical rendering in every release.
Hypothetical two-computer handoff
Hypothetical illustration—not a completed RawTherapee test: a merchant edits a copper kettle on Computer A. Its approved treatment is saved beside the RAW as kettle.raw.pp3. Computer B previously opened the same source and has an older cached treatment.
The merchant transfers the RAW and neighboring PP3 to Computer B. On reopening, the displayed kettle looks warmer than the approved export.
The proposed investigation compares the adjacent PP3, the cached settings and the configured precedence. If B loads the old cache treatment, the mismatch is a profile-selection problem. If B loads the approved PP3 but the rendering still differs, investigate application version and processing behavior instead.
No actual computer transfer or software result is claimed.
Make the approved profile portable
For each deliverable, retain the RAW, its approved processing profile, the RawTherapee version and a reference export. Give the profile an unambiguous identity rather than relying solely on the presence of a green thumbnail indicator.
Before transferring a batch, decide whether the receiving workflow should use image-adjacent profiles or a deliberately managed cache. Verify that decision on one representative file.
After reopening, compare the actual rendered output with the approved reference. Check product color, highlight treatment and crop, not merely whether a PP3 file exists.
If the original and profile disagree with the approved output, hold the handoff until the intended processing state is identified. A copied sidecar is evidence of settings, not independent proof that the recipient loaded them.
Record your own observations
The filled rows are illustrative examples. Use the blank row for your own files and observations.
| Hypothetical record | Location | Treatment | Question | Action |
|---|---|---|---|---|
| Kettle RAW | Transferred source folder | Unmodified capture | Exact original confirmed? | Preserve |
| Kettle PP3 | Beside RAW | Approved treatment from A | Is this selected? | Compare with reference export |
| Kettle cache profile | Computer B central cache | Older warmer treatment | Does precedence select this? | Resolve without destroying either version |
What the references establish
- RawPedia — Sidecar Files - Processing Profiles: Documents PP3 processing profiles, image-adjacent and central-cache storage, preference-controlled handling and version-compatibility considerations.
Sources and further reading
Recorded source-review dates are listed individually below. An undated source does not inherit the article’s publication date. Software and platform rules can change; check the current original before acting.
- RawPedia — Sidecar Files - Processing Profiles · Review date not separately recorded
Frequently asked questions
Is a PP3 file the edited photograph?
No. It contains RawTherapee processing settings applied when the photograph is developed.
Should I delete RawTherapee's cache to force the new edit?
Not as a first step. Inspect the storage and precedence preferences, preserve both profile versions and identify the approved treatment.
PREPARE ASSETS FOR YOUR NEXT STEP
Create supporting product assets in CartVisual.
Create new product creative assets in the workspace, then continue in your chosen tools. Third-party software procedures described in this guide take place in those applications; this workspace link does not imply an integration. Check current capabilities, account access and credit quotes.
Create account and open this workspace Check pricing and creditsStart with free concept and copy planning after sign-in. Image and video generation require available credits; review the quote before starting.
Already have an account? Open the workspace.