The Wait
To load a game on a ZX Spectrum, you pressed play on a cassette recorder and waited. The machine read data as audio — an unbroken screech of modulated tone — and the screen border strobed in bands of colour indicating what the computer was currently receiving: red and cyan while waiting for a header, yellow and blue while taking in header or data. This continued, typically, for several minutes.
And it could fail. A slightly stretched tape, a misaligned head, a volume level marginally wrong, and the load would collapse — sometimes at the very end, after four minutes of screeching, returning you to a blank screen and an error message and the necessity of rewinding and starting again. There was no diagnosis and no remedy other than trying once more and hoping.
Larger games made it worse. Multiload titles were split across multiple tape sides or multiple tapes, prompting the player mid-game to stop, flip the cassette, and wait again — a loading screen appearing between levels not as a design choice but as a physical errand.
Something to Look At
Into this dead time, developers put a picture. The loading screen was a full-screen image transmitted at the very start of the tape, which appeared — famously, unforgettably — line by line as the data arrived, and then sat there for the remaining minutes while the game itself loaded behind it.
It was not free. A Spectrum loading screen occupied around 6K, which on a 48K game meant roughly a 13% increase in loading time. Developers were deliberately making the wait longer in order to give the player something to look at during it, and it is difficult to think of a clearer statement of priorities: the experience of waiting was considered worth spending real resources on.
The line-by-line reveal became a ritual in its own right. Buying a new game and watching its loading screen resolve for the first time, stripe by stripe, was one of the genuine thrills of Spectrum ownership — a slow unveiling that no instant-loading medium can reproduce, because the pleasure was entirely a function of the delay.
The Gap Between the Picture and the Game
There was a catch, and everybody who lived through it knows exactly what it was. The loading screen was often the best-looking thing about the game.
Cassette inlays carried lavish airbrushed artwork — Bob Wakelin's covers for Ocean were miniature film posters — and the loading screen frequently attempted to reproduce something of that promise in Spectrum graphics. Then the game finished loading, and what appeared was a handful of monochrome blocks with attribute clash. The distance between the fantasy on the cassette box, the intermediate promise of the loading screen, and the reality of the running game was, for a great many titles, considerable.
This was not really dishonesty; it was the condition of the medium. Everybody was performing an imaginative translation, and the artwork existed to fuel it. But it does mean that a substantial part of the aesthetic memory of 8-bit gaming is composed of images that were never actually playable.
Waiting, Abolished
The loading screen as an art form died with the medium that necessitated it. Disks were faster; CDs were faster still; hard drives and solid-state storage have compressed the wait to the point where the modern loading screen is a spinner, a tip, or nothing at all. Nobody misses the four minutes of screeching, and nobody should.
But the cassette era produced something no efficient medium can: an enforced pause between the decision to play and the ability to play, which the game filled with an image, and which the player filled with anticipation. The load was the overture. It was the moment when the thing was arriving but had not yet arrived, when it could still be anything, and when a picture drawn one line at a time was the only evidence that something was coming.
The tape did eventually stop screeching. And then, if you were lucky and the volume was right, you played.