Are these NVIDIA DLSS 5 runtime screenshots?
No. These are independent before-and-after references from the DLSS5NVIDIA image pipeline. They are not NVIDIA captures and do not prove an in-game DLSS runtime result.
What does “before and after” mean here?
Each card keeps the input beside one output from the named workflow. The three low/high pairs show verified file dimensions; the retouch, cutout, erase and try-on cards show measured workflow runs with their controls and date.
Does upscaling recover factual detail?
No. It estimates a more usable visual result from the input. Faces, labels, numbers, thin geometry and repeated patterns can change, so compare them at 100% and keep the original.
Can I try the converter without an RTX GPU?
Yes. The browser workflow runs on the site service, so a modern browser is enough for a cached example or an account workflow. The separate DLSS5 Studio request page is a Windows RTX product and is still being developed.
Why is the retouch card not labelled as an upscale?
Its input and output are both 600 × 900. It is a same-size portrait retouch case, included to show the difference between restoring an existing image and enlarging it.
What inputs usually fail?
Extremely small or heavily compressed images, tiny text, multiple faces and scenes with motion blur are hard cases. Start with the largest original file, then inspect the result before sharing or publishing it.
How is this page different from the benchmark center?
This page is a visual gallery: it pairs existing inputs and outputs so you can inspect edges, faces and composition. The benchmark center defines measurement fields and separates recorded runs from visual references.
Can I reproduce one of these cases?
Yes. Open the linked tool on a comparable input, use the control shown on the card, and record the original file, output size, model or preset, hardware, driver, date and elapsed time. Results may vary between runs.
Why does this page not use NVIDIA screenshots?
The gallery documents our own image pipeline. Keeping independent assets separate from NVIDIA material makes the provenance clear and avoids presenting a visual reference as an official runtime capture.