Commodore 64 vs. VIC-20: nearly thirteen times the system RAM behind a familiar keyboard
The keyboard family resemblance hides different memory budgets, and a BASIC prompt’s free-byte count answers a narrower question.
The familiar keyboard shape does a fine job hiding the arithmetic. A Commodore 64 has 64 KB of system RAM; a VIC-20 has 5 KB. The difference is nearly thirteenfold before anyone adds an expansion cartridge or starts subtracting the memory used by the system.
Those figures come from the Commodore 64 and VIC-20 records. For this discontinued-hardware comparison they are identified as Wikipedia figures, rather than being dressed up as a fresh hardware measurement. The ratio is 64 ÷ 5 = 12.8.
| Decision row | Commodore 64 | Unexpanded VIC-20 |
|---|---|---|
| System RAM | 64 KB (Wikipedia) | 5 KB (Wikipedia) |
| Ratio basis | All installed system RAM | All installed system RAM |
| BASIC availability caveat | Part of installed total is exposed to BASIC (Wikipedia) | 3,583 bytes for BASIC programs and variables (Wikipedia) |
The installed total and the prompt’s available space answer different questions. The VIC-20 record says system functions and the display use part of its small store. Comparing that remaining 3,583-byte space with the C64’s entire installed memory would quietly give one machine a handicap and the other its full suitcase.
That distinction is familiar to anyone who has bought storage and then looked at the space left after setup. The machine’s headline capacity is real, but it does not describe every place a particular program can put its belongings. The keyboard cannot explain the lease agreement by itself.
The VIC-20 documentation summarized in its record adds another wrinkle: RAM cartridges change the memory map, and some software expects a particular amount of memory. More RAM is helpful only if the program finds the environment it expects. An expansion can change the room numbers while adding rooms.
That gives a collector a better decision than simply choosing the larger number. Someone interested in a specific VIC-20 program should check its expansion requirement and reproduce that arrangement. Someone looking for the C64 library should choose a C64-compatible environment rather than assuming the similar case makes the VIC a small substitute.
The machines’ relationship therefore cannot be reduced to a universal speed multiplier. Twelve-point-eight times the RAM does not promise twelve-point-eight times the performance, nor does it turn software for one machine into software for the other. Memory capacity and compatibility deserve separate rows on the shopping list (annoying, but cheaper).
For a reader who wants a particular title rather than original hardware, a lawful emulator or reissue can be the third option. It still needs the right machine configuration. The convenience of a modern host does not erase the old program’s assumptions about where memory and devices live.
As more retro collections package machines behind familiar interfaces, that configuration detail could become the part most worth preserving. The nostalgic keyboard invites the memory; the memory map decides what runs. The next cartridge somebody inserts may alter more than the amount shown at startup.
The cases kept the secret.