Every console versus PC thread has one: the comparison where the PS5 shot looks gray and washed out, someone declares PC the obvious winner, and three replies later it turns out the console screenshot was an HDR capture viewed on an SDR screen. The comparison was broken before anyone formed an opinion, and the argument runs another two hundred replies anyway.
Cross-platform comparisons are the hardest kind of graphics comparison to do fairly, harder than settings tests or mod showcases, because the two machines disagree about resolution, color, and even what “the same settings” means. Hard isn’t impossible. It’s a checklist.
The HDR trap, first, because it ruins the most comparisons
Consoles run HDR by default on most TVs. Screenshots captured in HDR carry color encoded for an HDR display, and the moment that file lands somewhere SDR, a Reddit post, a browser, most image tools, it gets flattened and comes out looking foggy and desaturated. The console isn’t rendering a gray image; the pipeline is mangling one.
The fix is blunt: turn HDR off on both machines before capturing, and take the comparison in SDR. You lose the HDR presentation, which is real, but an SDR-vs-SDR comparison is honest about everything else, while an HDR-flattened-vs-SDR one is honest about nothing. If HDR itself is the thing you want to compare, that needs a video pipeline built for it, and stills were never going to carry it anyway.
Getting matched frames out of two machines
The discipline is the same as any two-image comparison: identical scene, identical moment, one variable. Across platforms, that means:
- Find a repeatable spot. A save point, a photo mode scene, a cutscene the game renders in-engine, a bench at dawn after a save reload. Weather and time of day must match, so lean on saves and story moments where the game fixes both.
- Use photo mode if the game has one, on both platforms, same camera position. It pauses the world, kills the HUD, and its camera coordinates are the closest thing to a tripod two machines can share.
- Match the field of view. Many console versions lock FOV where PC exposes a slider; if the PC’s is adjustable, set it to the console’s value, or the geometry won’t line up and every close object will look “different” for reasons that have nothing to do with graphics power.
- Capture at the same output resolution, and mind dynamic resolution. Consoles routinely render at a varying internal resolution and output a fixed one; a busy combat frame and a calm vista can differ. Capture calm, static scenes so dynamic res has settled, and say in your labels which console mode you used, quality or performance, because those are effectively two different graphics cards.
- Native capture only. Console share buttons save proper screenshots; use those files, moved off the console however yours does it, not a phone photo of the TV and not a screenshot of a compressed stream. On PC, the game’s own screenshot key or an uncompressed Steam capture. PNG everywhere if the option exists.
That last point quietly disqualifies most comparisons you’ve seen: a huge share of “PS5 vs PC” images online are actually “YouTube compression vs YouTube compression.”
What settings should the PC even use?
Depends on the question you’re answering, and there are two fair ones.
“What does the console deliver relative to PC settings?” Match the experience: pick the PC preset that most resembles the console mode (digital foundry-style optimized settings threads exist for many games and can save you the guessing), then compare. Expect the result to be closer than the internet assumes, consoles punch at surprisingly specific mixes of medium-high.
“What’s the ceiling difference?” Max the PC out and compare against the console’s quality mode. That’s fair too, as long as the labels say so. What’s not fair is maxing the PC, comparing against the console’s performance mode, and captioning it “PC vs PS5.” Labels carry the honesty in this genre.
Note what doesn’t transfer: anti-aliasing and upscaling differ per platform (a console might use FSR or a dynamic-res TAA where the PC runs DLSS), and that alone changes image character. If upscalers are the interesting part for you, the DLSS, FSR, and TAA guide covers judging them properly.
Put the pair under a slider, not side by side
Cross-platform differences are mostly subtle: texture filtering, shadow resolution, foliage density, draw distance in the far field. Side-by-side viewing at forum-thumbnail size hides all of it. Stack the two captures under a before and after slider instead, label the sides (“PS5 quality mode” / “RTX 4070, optimized settings”), and let people drag across the tree line themselves:
Upload both files at imgi.co, free, no account, and it serves your exact uploaded bytes with no re-encoding, which matters here more than anywhere; a comparison site that recompresses your captures would be adding its own platform to the test. One comparison holds up to ten images, so PS5 performance, PS5 quality, and three PC presets can live under one slider with a dropdown. For posting where embeds don’t run, export the GIF or MP4 and put the interactive link in a comment.
The comparisons worth making
The tired one is “which box wins,” and stills were never going to settle it, because half the real difference is framerate and stills don’t have one; say so when you post, it’s the disclaimer that keeps the thread civil. The useful ones: is quality mode visibly better than performance mode on your TV, from your couch? Does the PC’s ultra preset actually beat the console’s quality mode, or just its framerate? Is the cross-platform game you’re about to buy meaningfully prettier on the machine you don’t own yet? Those have answers, your captures can carry them, and a fair pair under a slider ends the argument instead of feeding it.