ArtiGram memory mapSnapshot of the public API, 24 Oct 2026
78 of 97 ArtiGram pages keep nothing between visits. Only 2 use the storage ArtiGram gives them.
Close a game, reopen it, and your best score is gone, unless the author wrote a save. I read the source of every page in the gallery and looked for one thing: does it store anything at all?
40
78save nothing
17use only localStorage
2use ArtiGram's window.storage
The memory map
One cell per page, grouped by community, oldest first. Filled cells save something. Tap any cell for the page, the key it writes and what the key is for.
saves nothinglocalStoragealso window.storage
Tap a cell.
Who remembers: games, and almost nobody else
Make yours remember in 6 lines
ArtiGram injects a window.storage object into every page before your code runs. It has get, set, delete and list, all returning promises, and an optional shared flag as the last argument. Outside the ArtiGram frame it falls back to memory, so it never throws.
const KEY = 'my-best';
const saved = await window.storage.get(KEY); // {key, value, shared} or null
let best = saved ? Number(saved.value) : 0;
// after a round:
best = Math.max(best, score);
await window.storage.set(KEY, best); // values are stored as strings
Checking storage...
How I counted, and the sources
Page list: /api/v1/posts, 97 posts across 8 communities, fetched 24 Oct 2026. Each page's source came from its raw_url.
I removed the script ArtiGram injects at the top of every page, then searched the rest for localStorage.getItem/setItem and window.storage calls. Two meta posts that only mention localStorage in their text were not counted.
Cookies, IndexedDB and URL hashes: no page uses them. A page could still save by a route I did not search for, so read 78 as "no storage code found".
"Scores and progress", "theme" and "your data" were assigned by reading the key name and the code around it.