Borderlands 4 silently removed Denuvo: where did the +20 FPS come from?
Update 1.11 cut 171 MB from the executable, but the same patch shipped performance work and 2K's own DRM still runs, so nobody can yet say how much of the gain was Denuvo.
The official notes for Borderlands 4 Version 1.11, released October 22, 2026, cover Story Pack 2 fixes, balance changes for Loveless and other Vault Hunters, boss adjustments and a long list of mission repairs. The words Denuvo and anti-tamper appear nowhere in them. Neither 2K nor Gearbox has confirmed any change to the protection.
The executable tells a different story. SteamDB data shows Borderlands4.exe shrank by about 171.69 MB after the update, and several packages disappeared from the depot. TechPowerUp, PC Games Hardware and VGTimes all checked the same depot data and reached the same conclusion: Denuvo is gone from the binary. EpicNNG, a content creator who covers the series closely, summed it up:
Until I hear from an official source, it would indeed appear that today's update for Borderlands 4 has removed Denuvo from the exe. Symbiote (2K's DRM) appears to still be in place.
That second sentence matters as much as the first. Symbiote, 2K's in-house protection layer, is still running after the patch. Patch note lists and shipped binaries can disagree; we documented a similar gap in our Phantom Blade Zero patch audit.
The frame rate numbers in circulation
EpicNNG tested the game at 1440p on medium settings and measured roughly 50 FPS before the patch and 70 to 80 FPS after. That is the figure most headlines ran with. iXBT games cites a second test by PlayWithEsh on a laptop RTX 3050 Ti with 4 GB of VRAM: 40 to 60 FPS on low settings, with occasional drops. TechPowerUp points out that no controlled benchmark data exists for any of this, and players continue to report sudden dips after updating. PC Gamer, as summarized by CanIRun, reports Gearbox tying the new stutter complaints to shader compilation that should settle as it finishes.
So the observed post-patch range is wide, and the strongest number comes from one creator's test on one machine.
Why the attribution is shaky
Denuvo's measured cost has never approached 40 percent. PC Games Hardware, which has lab-tested Denuvo titles for years, puts the historical impact on CPU-bound frame rates at five percent at most. Our own six-game benchmark from last week, run with identical builds and frame-time capture, measured average frame rate drops of 1.8 to 4.2 percent with Denuvo enabled, with 1% low drops of 8 to 19 percent. Those numbers describe what removing Denuvo can give back. A jump from 50 to 70-plus FPS at medium settings is an order of magnitude larger than anything in that data.
Version 1.11 also shipped performance and stability improvements of its own, listed in the notes without detail. Part of the gain is therefore unattributed by design.
And Symbiote still runs. If 2K's in-house layer carries a meaningful CPU cost, that cost remained in place while Denuvo was lifted out.
The most defensible reading: the optimization pass did most of the work, Denuvo's removal added some unknown share, and the tail behavior deserves more attention than the average frame rate everyone quoted. Average FPS was never where Denuvo's cost showed up.
The removal itself fits a pattern
The protection had already lost its job before the patch. In mid-February 2026, a hacker using the handle Kirigiri demonstrated a hypervisor-based bypass of Borderlands 4 on version 1.3.0, as reported by iXBT games and TheGamer. The method got past Denuvo, Symbiote and Steam's own DRM at once, at the cost of disabling Windows security features on the machine running it. VGTimes reports that a cracked build appeared on torrent sites again shortly after update 1.11.
Publishers commonly pay per-title fees for Denuvo and drop it months after launch once the launch sales window has closed, and those removals are usually announced. Nobody outside the two companies knows why this one went unannounced, or why the patch notes stay silent on a change this visible.
What would settle it
We have not run Borderlands 4. Every number above belongs to someone else: SteamDB for the binary size, EpicNNG and PlayWithEsh for frame rates, PC Games Hardware and our own benchmark for what Denuvo costs in controlled conditions. A proper answer needs one machine, one save file, identical settings, and frame-time capture with attention to 1% lows, which is the method we used in our Denuvo benchmark. Until somebody publishes that comparison, the honest summary is: the executable got smaller, some frame rates improved, and the split between the optimization pass and the DRM removal is still unknown.
