September 2023, update 2.0: the perk trees rebuilt from scratch, cyberware reworked, police chases added, system requirements raised — and every native mod broken at once. For three years of patches before that, an enormous mod ecosystem had grown around the 1.6x line, and chunks of it never crossed the 2.0 boundary. That's audience one: people whose mod stack lives in 1.63. Audience two is hardware: 2.x is simply heavier, and 1.63 was the last version with Static Resolution Scaling — the override-anything-up-to-200% knob that made the game playable on machines the new requirements left behind. Audience three just prefers the pre-rework game they finished three times. And separately from all of them: 2.x players who want to pin a specific 2.x patch, because the updates didn't stop and neither did the mod breakage — the cycle repeats on every 2.2x release.
One structural fact upfront: Phantom Liberty requires the 2.x line. Downgrading to 1.63 means the expansion's content is off the table for that install — there is no 1.63-with-PL configuration, on any platform.
01Saves: strictly forward
%USERPROFILE%\Saved Games\CD Projekt Red\Cyberpunk 2077\ somewhere safe before any version move and disable cloud saves for the game while you're off the current patch, or sync will keep pushing 2.x saves at a build that can't read them. If you keep era saves around (a pre-2.0 backup from 2023 counts), label them — future you won't remember which folder loads where.
02The official shelf — use it first
CDPR is one of the few studios that answered the downgrade demand directly, and their support page says so officially:
| Platform | What you get |
|---|---|
| Steam | Properties → Betas → 1_63_legacy_patch. The modding wiki notes selected 2.x point versions surface there too as branches. Switching back = pick "None". |
| GOG | The best rollback on any store: Galaxy's Manage Installation → Configure has a literal version picker plus per-game auto-update toggle — CDPR's own platform, DRM-free. |
| Epic | Nothing. CDPR's own words: only the latest version is available. No branches, no rollback, and no DepotDownloader either — it's a Steam-infrastructure tool. |
If 1.63 is your destination and you're on Steam or GOG, that table is the whole tutorial. DepotDownloader can also pull the Steam branch into its own folder — handy for keeping 1.63 and current installed side by side instead of letting Steam swap them:
> .\DepotDownloader.exe -app 1091500 -branch 1_63_legacy_patch -username you -dir .\cp77-163To pin your main Steam install on any version: updates to "only when I launch" plus the read-only trick on appmanifest_1091500.acf — which is exactly what the modding community's own wiki recommends for this game.
03DepotDownloader for the gaps
The shelf holds a few versions; the patch history holds dozens. For a specific 2.x build the branches skip — yesterday's patch before it broke your framework stack, the exact version a mod list names — it's manifest work, and the RED Modding wiki maintains the version→manifest tables so you rarely need raw SteamDB archaeology (recent examples from their list: 2.3 base content 6814019010317238099, 2.21 8420445566849588826, both for depot 1091501).
The Cyberpunk-specific wrinkle is that a complete install is several depots from the same era: base content (1091501), your language packs, and on 2.x — Phantom Liberty's content and the REDmod depot if you use it. Mixing eras across those is the classic self-inflicted crash — it's exactly what bit me the first time, when I matched the base depot but left Phantom Liberty on the newer manifest. The wiki's tables pair them; take the whole row, feed the lists to one command:
> .\DepotDownloader.exe -app 1091500 -depot 1091501 <more-depots> -manifest <id> <more-ids> \
-username you -remember-password -dir .\cp77-pinnedBudget for it: this is an 80+ GB game, and a pinned copy is a second full install. Launch from the folder with Steam running; GOG-rollback users skip all of this — their version picker fetches official old builds directly.
04The framework-era rule
What actually decides whether a downgraded Cyberpunk works is the mod plumbing. Nearly everything interesting sits on a framework stack — Cyber Engine Tweaks, red4ext, redscript, ArchiveXL and friends — and every layer of it is locked to the game binary, the same way SKSE is to Skyrim's. The wiki's blunt rule is "always make sure your framework mods are up-to-date", and for a pinned old build that means up-to-date for that era: Nexus keeps every mod's old files tab, the frameworks' GitHub releases are versioned, and the working combination is era-correct everything — game, frameworks, then mods, in that order. Half-upgraded stacks produce the crash-on-launch threads that fill the forums after every patch; a downgrade just runs that movie in reverse if you let it. The same era-matching discipline carries over to other big modded RPGs whose hotfixes routinely break the loader — Baldur's Gate 3 is the current poster child, with Script Extender pinned to each patch just as these frameworks are.
05Status in 2026
Cyberpunk is among the safest downgrades on this site, for one reason: the main destinations are live branches, not historical manifests. 1_63_legacy_patch is served fresh by Valve's CDN on request — manifest weather doesn't apply to it, and GOG's picker is CDPR's own infrastructure. Only the in-between 2.x point versions ride on old-manifest availability, and those are recent enough to be the friendly case. The cautionary tale in this game's table is Epic: same game, same money, zero version access — which store you buy on is a preservation decision, and Cyberpunk states it more plainly than any other page here. If your platform gives you a shelf, use it; if it doesn't, the folder you archive yourself is the shelf. If it were my call, I'd take the official 1_63_legacy_patch branch over hand-matched manifests every time it covers your target — it's the one piece here I don't have to babysit.