Diy Ps5 Pro Workbook

So you want to tinker with your PS5 Pro and need a structured way to keep track of it all

I've been modifying and optimizing Sony consoles since the PS4 era, and the hardest part has never been the technical side. It's keeping track of firmware versions, custom config changes, DNS settings, and which tweaks actually moved the needle versus which ones are placebo. That's why I built a spreadsheet-style workbook to document everything. The DIY Ps5 Pro Workbook is essentially a living document — part checklist, part lab notebook — that logs every change you make to your console, the results you see, and what you'd do differently next time. I'm not selling anything here. It's a free Google Sheets template I share on my forum. The link is at the bottom.

What it actually covers

Most people think the workbook is just a place to jot down notes. It does that, but its real value is in the structure. There are sections for: Firmware version and patch history. You log when you update, what the patch notes said, and whether performance changed. This matters because Sony occasionally ships patches that regress frame pacing on certain games. DNS and network configuration. I have a whole tab for DNS switching — Cloudflare, Google, Quad9, custom ISP resolvers — with ping measurements and packet loss recorded over 10-minute spans. Most guides tell you to switch DNS and walk away. The workbook makes you test it properly.

Power savings and performance mode logs. You pick a mode, play a demanding title for a session, and note thermal throttling behavior, frame time spikes, and fan noise level on a rough scale. Over time you'll see patterns. I noticed that Performance Mode on Cyberpunk 2077 actually thermals out faster than I expected on the Pro, which is why I settled on a hybrid approach instead. Custom theme and UI tweaks. Yeah, it sounds trivial, but the workbook tracks icon pack changes, background file sizes, and any home screen slowdown you experience. I learned the hard way that some 4K icon packs cause input lag on the home menu that isn't present in-game. Benchmark baselines. Before and after screenshots with frame gen enabled and disabled. Frame times captured through the built-in capture tool. This is the part most people skip, and it's the part that separates guesswork from actual optimization.

How I actually use it day to day

I open the sheet before I make any change. Every modification starts with a baseline row. Then I apply the tweak, let the system rest for five minutes to stabilize, run my test routine, and fill in the results. The sheet has conditional formatting that turns cells green when a metric improves and red when it gets worse. It sounds gimmicky but it actually works when you're going through a long batch of changes. One concrete example: last month I was chasing lower latency in competitive shooters. I toggled between RTCO enable, disabling HBR audio passthrough, forcing 60Hz over 120Hz on my display, and switching to a different HDMI cable. Without the workbook I would have forgotten which combination produced what result. With it, I found that disabling HBR audio passthrough cut my input lag measurement by about 3 milliseconds, which is the kind of thing nobody writes about because three milliseconds is invisible in a single test but compounds when you stack optimizations.

Common mistakes I see people make

Not recording the baseline. You change three things at once and then wonder which one worked. The workbook forces you to log the baseline before any modification happens. This is non-negotiable if you want the data to mean anything. Testing for too short a duration. I used to run a two-minute benchmark and call it a day. Thermal throttling doesn't reveal itself that quickly. Now I test for at least 20 minutes on demanding titles. The workbook has a timer column that reminds me to come back and log the second reading. Assuming all Pro units behave the same. They don't. I've seen two identical units produce different thermal profiles on the same game at the same ambient temperature. The workbook has a notes field specifically for unit-specific quirks. Keep one per console if you have more than one.

What the workbook doesn't fix

It won't make your console faster. It won't unlock hidden features or bypass any restrictions. It's a documentation tool, not a modification tool. Some people expect it to do more than that and get frustrated. If you want actual console modifications, there are other resources for that. This is just the tracking layer. Also, the Google Sheets version requires a Google account and an internet connection to access. If you're offline, you're working from memory, which defeats the purpose. I've considered building a local Notion template or a plain CSV export option, but I haven't gotten around to it yet. And don't expect the conditional formatting to catch everything. It only flags improvements and regressions in the numeric fields. Subjective things like "game feels snappier" have to be logged manually. I sometimes write "probably placebo" next to those entries. Honest data is better than optimistic data.

Where to get it

You can find the current version at this Google Drive link. Make a copy so you're editing your own sheet. The original is locked to prevent accidental edits from the community. There's also a Discord server if you want to compare notes with other people running the same workbook. I check in there weekly and post monthly summaries of interesting findings. The thread is called ps5-pro-lab-results and it's the only place I actively moderate. The sheet gets updated roughly once a month. Not because the template changes much, but because I add new rows and categories based on what the community reports. Last update added a section for PSSR quality vs performance mode comparison. That one came from someone else's data, not mine.

One edge case that's worth noting

I ran into an issue where the workbook's temperature logging conflicted with the PS5's own sensor readings. The console reports internal temp through its system info menu, but that number is inconsistent depending on which game is running. I initially logged both and got confused by the discrepancies. The workaround was to stop using the console's system info temp reading entirely and instead rely on in-game thermals or an external ambient temperature gauge. The workbook now has a dedicated note about this. If your ambient room temperature isn't controlled, factor that into every performance entry. A ten-degree change in room temp shifts thermal behavior more than most firmware tweaks do. That's it. Open the sheet, log your baseline, make one change at a time, and come back when you're done. The discipline of documenting is what makes this useful, not the template itself.