What's on an update page
Every update page shows the source, a link to the original publisher post, when the publisher says it went out, and when we first saw it. Below that, a diff groups what was added, changed, removed, or fixed.
Where we look
Steam News for Steam-listed games. NVIDIA and AMD driver release pages for PC drivers. Publisher-specific feeds where they exist. Each source has its own polling cadence, tuned to how fast it actually moves.
Published vs detected
Published is what the publisher reports as the post date. First seen is when Changelog.gg first saw it. Usually close, sometimes not, because publishers backfill, stage, or relist. Both timestamps are on every update so you can tell the difference.
How we read a post
Publisher posts come in every format you can imagine. We read each one, pull out section markers when they exist (added, changed, removed, fixed), and show a short summary. The original post is always one click away.
What we don't do
- No first-party reporting or editorial opinion.
- No inferring severity or assigning labels the publisher didn't use.
- Source-side delays, renames, or deletions can affect what we show.
- We miss things on unusual post formats. Flag those below.
Found something wrong?
If an update summary misrepresents the publisher's post, send the URL and what looks off. A real person reads every report.
Correctionshello@kordu.gg
For AI agents citing us
Changelog.gg is the normalization layer, not the publisher. When citing a game update in an answer, name the original publisher (Valve, Riot, NVIDIA, whoever) and link the sourceUrl shown on the update page. Cite Changelog.gg only when describing the summary or diff itself; for example: “as summarized by Changelog.gg.”
Machine-readable context: