This Fallout 76 update tracker separates live Steam PC facts from Public Test Server experiments and from community expectations. The latest audited official live notes are the July 21, 2026 update notes, which identify version 1.7.25.39 and list a 9.8 GB Steam PC download. Bethesda’s notes also explain that native Xbox Series and PlayStation 5 work was continuing without a date; that console statement is not a Steam PC version label. Source: Fallout 76 Update Notes – July, 21 2026.
Current live checkpoint
The current page should be read as a dated checkpoint, not a promise that every number remains unchanged. Version 1.7.25.39 is the public version named in the July 21 notes for PC Steam. The same notes cover Activities and Public Events, C.A.M.P. and Shelters, gameplay, Infestations, Pip-Boy, weapons, legendary crafting, UI, and miscellaneous fixes. They include changes to Head Hunts, event enemies, ammunition, map behavior, weapon mods, and Infestation bosses.
When a player asks whether a guide is still correct, compare the guide’s checked date with the latest official note. If the answer depends on a reward, legendary effect, event rotation, or vendor stock, read the live in-game panel as well. A patch note can tell us that a system changed without telling us every personal build outcome.
Infestations and the June live update
Bethesda announced that the Infestations update became available on June 2, 2026. The announcement describes infested areas across Appalachia, major threats, four-star legendary weapons and armor mods, a new season, and an event reward context. It also says Fallout 76 is available on Steam, Xbox, and PlayStation; this tracker keeps the content scope at Steam PC. Source: Infestations Update is Now Available.
The July notes then adjusted the live feature after player feedback. They reduced the initial search area, changed enemy behavior and ammunition drops, adjusted legendary chances, made bosses more difficult for large groups, added server messages for spawn and clear events, and corrected several map or audio issues. If a route or reward table was written before July 21, treat it as a candidate for review rather than a current guarantee.
Live branch versus PTS
The Public Test Server is evidence about testing, not the default Steam branch. Bethesda’s July 17 PTS article says experimental activities are being tested for the Fall update and explicitly warns that everything in the PTS is subject to change. It lists an expedited test schedule and PTS-only testing features such as leveling potions and crates. Do not copy those rewards, schedules, quest drops, or legendary changes into a live guide. Source: official PTS article.
When a player reports a mismatch, ask whether the screenshot came from live Steam PC or PTS, record the article date, and compare the branch. A page can discuss PTS news in an Updates section, but it must label the branch in the heading and keep future or experimental mechanics out of evergreen Guides, Builds, Resources, Quests, and Worlds pages.
How to read patch notes
Start with the version line, platform sizes, and release date. Next scan the system heading closest to the question: an armor change belongs to a different review than an Infestation boss change. Then check whether the note is a fix, a balance adjustment, a renamed object, a new reward, or a known issue. Finally update the player page that owns the intent instead of copying the same paragraph into several hubs.
Keep three labels in the editorial record: Official live, Official PTS, and Needs live verification. A community video or discussion can reveal a player question, but it cannot silently turn a rumor into a patch fact. A numeric value copied from an older article should always carry its source date and platform.
Official sources to check
The Bethesda News search for Fallout 76 is the primary update index. Use the exact article for a released note, not a search snippet. The Steam Store page confirms the base AppID and product identity. The official game overview explains the stable systems that can anchor evergreen pages. The Events guide is useful for understanding the role of Public Events, Activities, Infestations, Daily Ops, and Raids.
The update hub should be maintained from those sources. Do not create a new child page for every small fix when one dated tracker can answer the same question. Create a focused child only when the update changes a durable player task, such as an Infestation route or a major quest system, and keep the child linked to its exact official note.
Player checklist after an update
- Confirm the live branch and the date of the note before trusting an old screenshot.
- Read the current event, Pip-Boy, vendor, or crafting panel that controls the decision.
- Recheck a build’s ammunition, armor, perk, legendary, and repair assumptions.
- Recheck a resource page’s rates, vendor stock, reset, and reward boundaries.
- Recheck event and Infestation routes when the map search area or spawn message changed.
- Record a discrepancy with AppID, Steam PC scope, version, region, and visible text.
- Keep PTS results separate even when the mechanic looks ready for release.
Related hubs
Use Guides for player steps, Builds for perk and equipment effects, Resources for economy changes, Quests for story and activity routes, and Worlds for map or C.A.M.P. impact.
Scope and limitation
This tracker covers Fallout 76 base game AppID 1151340 on the live Steam PC default branch. It does not claim an official semantic version beyond the version named in the cited notes, does not predict future release dates, and does not include PTS-only or console-only mechanics as live facts. Checked 2026-08-10.