The 2024 ROG Ally X’s 24GB memory figure is system RAM, not a separate 24GB graphics-memory allocation; its 1TB SSD serves a different purpose. Buyers can make a clearer decision by separating their working-memory needs from their installed-game library. This is an English documentation-based guide to the model announced globally from Taipei on 2 June 2024, with the primary announcement checked on 3 October 2026. It does not describe a newer Ally generation.
Read the announcement by component
ASUS’s dated ROG Ally X announcement identifies an AMD Ryzen Z1 Extreme processor, 24GB LPDDR5X-7500 RAM and a 1TB M.2 2280 SSD. It explicitly describes the APU’s video memory as shared with system RAM. Those statements identify the announced configuration; promotional performance language is not an independent benchmark, and the article does not adopt it as one.
Build a library budget before a memory argument
Start with the games and non-game files you expect to keep installed. Use their current publisher or installer requirements when making a storage worksheet, then allow for the operating system, updates and your own files. This is a planning exercise rather than an estimate of the free capacity on an unopened device. We have not measured usable storage, and advertised capacity should not be relabeled as space already available to games.
A separate worksheet should describe what you expect to run together. A game, communications application and background work represent a different question from how many games fit in the library. Adding SSD capacity does not answer that working-memory question. Equally, the RAM number does not tell you how many large installations can stay on disk.
| Question | Relevant announced field | Decision boundary |
|---|---|---|
| What can remain installed? | SSD capacity | Use current installation sizes and leave a planning margin |
| How is working memory organized? | System RAM shared with the APU | Do not describe all system RAM as dedicated graphics memory |
| How fast does a named game run? | Not established here | Obtain comparable measurements rather than converting capacity to speed |
A useful comparison starts with the bottleneck
Our editorial preference is to identify the unresolved constraint before comparing models. A buyer constantly choosing which installations to retain has a storage-management question. A buyer asking about a particular workload needs evidence about that workload. These concerns can coexist, but merging them into a single larger-is-better number makes a comparison less informative.
Do not calculate a recommended graphics allocation from this announcement alone. The document describes the shared architecture; it does not validate an optimal allocation for your applications. Similarly, an M.2 form-factor statement is not an instruction to open the device or a guarantee about arbitrary replacement drives. This guide addresses purchase interpretation and contains no modification procedure.
Keep the year and market attached
The announcement is historical primary evidence for the 2024 configuration. It does not establish a current regional offer, warranty or price. Needs editor verification: exact model-year identity in the seller listing, local bundle contents, usable capacity and any claimed performance improvement. A newer product sharing parts of the name requires its own record.
No handheld was tested for this guide. Our Editorial Policy separates documented component identity from testing and purchasing judgment. The practical recommendation is to maintain two budgets, storage and working memory, then request evidence for the actual unresolved need.
Leave a Reply