VERSIONHISTORY

How to Use the Version History

The page reads top to bottom, newest first. The Current Version card at the top shows the latest build, its release date, the full download size, the installed size, and the patch size when one exists. Below it, the Release Timeline lists every tracked build, currently 8, running from v1.0.13 on January 22, 2026 to v1.4.5. The Launcher Info panel at the bottom shows the launcher version and the date the data last synced.

Each timeline card has the same layout, so once you can read one you can read them all. The version number and release date sit on the left, and the download and installed sizes sit on the right. If a patch exists, a line underneath shows its size and which version it patches from. The row of tags at the bottom lists the resource version each platform received for that build.

Most players come here for one of three reasons. You want to know how big the next download will be, you want to check whether your platform has the same build as everyone else, or you want to date a change to a specific version. The sections below cover how to read each part of the data for those jobs.

Reading Download, Installed, and Patch Sizes

Three sizes appear on every entry, and they answer different questions. Download is the packed size, meaning the compressed bundles a fresh install pulls over the network. Installed is the unpacked size, meaning the space the game takes on disk after extraction. For the current build, that is 49.70 GiB to download and 54.66 GiB installed, so plan storage around the larger number.

The patch size matters more if you already have the game installed. It shows the delta update from the version named on that line, and it can be far smaller than a full download. The gap between v1.0.13 and v1.0.14 was a 253.81 MiB patch, while the move from v1.0.14 to v1.1.9 was a 35.55 GiB patch. A small point release can cost a few hundred megabytes, while a jump to a new major version can approach the size of a full install.

Note that the "patch from" version is not always the build directly before it. The archive records the delta from a specific earlier version, so a recent entry may list a patch from a build several versions back. Read that line as "coming from this version, expect this download," and use it as a rough guide if you are updating from somewhere else.

What the Platform Resource Versions Mean

The colored tags under each entry show the resource version for Windows, Android, iOS, and PlayStation. A resource version identifies the exact asset bundle a platform loaded. The archive stores it as a longer string, and the page trims it to the part that follows "main_" to keep the tags readable. Two platforms with the same tag are running the same assets for that build.

Tags often differ between platforms on the same version. On v1.4.5, Windows, Android, and PlayStation share 8692565-6 while iOS shows 8692565-11, and older builds show similar splits. Each platform ships through its own store process, so platforms can be briefly out of step during a rollout. If a friend on another platform sees content you do not, compare your tags here first.

The launcher version is tracked on its own because launcher updates are not always coupled to game-data updates. You will find it in the Launcher Info panel, currently v1.5.0, next to the date the data last synced. If you are troubleshooting a PC install, check both numbers, since a launcher update can land without a new game version and the reverse is also true.

Using the Timeline Alongside Patch Notes

The timeline tells you when a build shipped, not what was in it. The data comes from the open-source ak-endfield-api-archive, which pulls from Hypergryph's CDN, so the dates reflect what actually shipped rather than announcement dates. That makes it a reliable anchor when you are trying to pin down exactly when something changed.

For content, pair it with the site's other trackers. The patch notes page covers what each update changed, and the banner history shows which operators and weapons ran in each period. Match a release date here to an entry there and you can tell which build introduced a banner or a balance change.

For planning ahead, the timeline is also a quick way to see the gap between versions. Look at the dates between major builds to get a sense of pacing, then use the pull income sheet to estimate how much currency you will earn before the next one. When a large patch is coming, clear storage in advance so the update does not fail partway through.