PRODUCT CREATIVE / PRODUCTION AND HANDOFF
Why does Topaz Photo lose RAW Denoise when I send my product photograph from Photoshop?
Topaz Photo RAW Denoise requires a supported original out-of-camera Bayer RAW file. A Photoshop layer or rendered TIFF is not equivalent to that sensor-data input, even if it originated from a RAW photograph. If RAW-stage noise treatment is required, plan the Topaz operation before the Photoshop handoff. If only rendered artwork remains, evaluate the appropriate standard Denoise workflow instead.
Identify what Photoshop actually sends
A merchant may open a camera RAW photograph in Photoshop, add product retouching layers, and then send the working image to Topaz Photo. The editor expects RAW Denoise because the photograph originally came from a camera RAW file.
However, the object reaching Topaz may now be a rendered Photoshop layer or TIFF. That representation no longer provides the same original Bayer mosaic data required by RAW Denoise.
A photograph's history does not determine its current processing eligibility. The relevant question is whether Topaz receives the supported out-of-camera RAW file or a rendered derivative.
Inspect the actual handoff object before concluding that the RAW model has disappeared because of a software defect.
Changing a rendered file's extension to DNG cannot reconstruct the original sensor mosaic.
Choose the RAW-stage or rendered-image route
When the original supported Bayer RAW is available and RAW-stage noise reduction is important, Topaz recommends processing that camera file first, exporting the result as DNG, and then continuing approved retouching in Photoshop or Photoshop Elements.
This sequence places RAW Denoise before the workflow turns the photograph into a conventional edited image.
If the merchant only has an approved JPEG, TIFF, or composited Photoshop result, the correct decision is different. Evaluate standard Denoise where appropriate, or request the original camera file if RAW-stage treatment is essential.
Do not discard completed retouching simply because the current representation cannot use RAW Denoise. Determine whether rebuilding from the original is justified by the actual production requirement.
X-Trans low-light noise has a separate standard Denoise consideration. Do not assume every camera from one manufacturer uses the same sensor pattern.
Illustrative exercise: available RAW versus finished composite
Illustrative exercise with fictional merchant inputs. No Topaz operation, denoising or image-quality test was executed.
Input A is a dark product photograph captured as a supported Bayer RAW. The original camera file remains available, and the merchant has not yet completed Photoshop retouching.
The team can evaluate the recommended RAW-first sequence: process the original in Topaz, export the appropriate DNG, and then continue the approved Photoshop work.
Input B is a supplier-delivered cosmetics advertisement available only as a composited TIFF. It contains finished typography, product cleanup, and decorative elements.
The team should not treat that TIFF as recoverable camera RAW. Evaluate ordinary Denoise on an appropriate working version, or request the original capture if the brief specifically requires RAW-stage processing.
Neither branch guarantees a particular noise reduction result.
Keep the handoff representation explicit
For each product photograph, distinguish the original camera capture, the Topaz-processed result, and the Photoshop working composite.
When RAW Denoise is unavailable, identify which representation entered Topaz. A rendered layer is a different input from the original mosaic file.
If ordinary Denoise is selected, review the product's visible texture and details without assuming the RAW-specific model would have produced a superior result.
Topaz warns that using an unsuitable denoising pipeline for RAW-stage noise can introduce artifacts. This is not evidence that every TIFF or JPEG denoising operation creates artifacts.
The handoff is complete when the editor knows whether RAW-stage processing is still possible or whether the remaining task concerns already rendered pixels.
Actual eligibility depends on the supported input and current application behavior, not merely the camera brand or filename.
Illustrative exercise — Topaz RAW-stage versus rendered-image handoff
These are illustrative exercise rows. Save a copy and record your own observations; the example is not an executed acceptance test.
| Fictional product | Available source | Editing stage | Merchant decision | Completion condition |
|---|---|---|---|---|
| A: Dark product photograph | Original supported Bayer RAW | Before Photoshop retouching | Evaluate Topaz RAW Denoise first, then DNG handoff | RAW-stage treatment considered before compositing |
| B: Supplier cosmetics advertisement | Approved composited TIFF only | After typography and retouching | Evaluate standard Denoise or request original capture if essential | Rendered artwork is not misrepresented as original camera RAW |
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.
Frequently asked questions
Why is RAW Denoise unavailable after sending a Photoshop layer to Topaz?
The layer may be rendered image data rather than the original out-of-camera Bayer RAW required by RAW Denoise.
Can I rename a supplier TIFF to DNG to enable RAW Denoise?
No. Renaming or changing the container does not recreate the original sensor mosaic information.
PREPARE ASSETS FOR YOUR NEXT STEP
Create supporting product assets in Itemlume.
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.
Explore asset creation tools Check pricing and credits