RTTTL: A Text String Someone Could SMS You

Nokia's plain-text format that turned melody into a message

Before ringtone shops, WAP portals or premium SMS short codes, there was a string of characters you could type into a Nokia's composer by hand — or, if someone was generous, receive directly as an SMS. Ring Tone Transfer Language, universally abbreviated as RTTTL, was Nokia's own specification for encoding a monophonic melody as plain ASCII text, and its elegant simplicity made it one of the small accidents of the mobile era that outlived its original purpose.

The format itself

An RTTTL string has three sections, separated by colons. The first is a name — up to ten characters identifying the tune. The second is a default block setting the tempo (in beats per minute), the default note duration, and the default octave. The third and longest section is the note sequence itself: a comma-separated list of duration-plus-pitch-plus-octave tokens. A note might render as 8e6 — an eighth note, the pitch E, in the sixth octave — and the whole encoding for a familiar four-bar melody might come in under a couple of hundred characters: well within a single 160-character SMS when compressed, and transmissible across several if not. Nokia created the format to allow tunes to be shared between compatible handsets, documented it publicly, and built RTTTL import into a succession of devices across the late 1990s and early 2000s, among them the Nokia 3310 and its Composer feature.

The specification is deliberately unambitious. RTTTL encodes pitch, duration and octave; it says nothing about timbre, dynamics or harmony. Every note is played by one voice on one speaker. That constraint is exactly what made it transferable: there was nothing platform-specific to trip over, no proprietary chip required, no binary header to misparse. A string that decoded correctly on a Nokia 3210 decoded correctly on a 3310, a 6110 or any other RTTTL-capable handset.

Before WAP, the web did the distributing

Nokia launched RTTTL publicly in 1998, and within months, enthusiast communities were doing something Nokia had not specifically planned for: they were posting strings to early web forums and personal homepages as plain text. A visitor would read the string on a desktop PC screen, copy it down — sometimes literally with a pen — and then key it into the phone's composer by hand. The composer would parse it and the tune would play. This was not a download in any commercial sense; it was transcription, the same thing musicians had done for centuries with sheet music, now conducted across a dial-up connection.

The strings circulated freely because they contained no audio data — just notation. Copyright law as it applied to ringtones in 1998 was unsettled and, practically speaking, unenforced at the level of a hobbyist's GeoCities page. Sites appeared in Finland, Sweden, Germany and the United Kingdom listing hundreds of RTTTL strings for television themes, film scores and chart hits. The informal economy that those pages represented would later be formalised — and monetised — by carriers and aggregators, but in the late 1990s it was just fans sharing something they had figured out.

When WAP arrived and handsets gained rudimentary mobile browsers, the same strings could be served over the air, and some carriers quietly began packaging RTTTL content as an early premium offering. But the format's roots were always in that open, unmonetised text-file culture. The Internet Archive holds captures of early ringtone listing pages ↗ from this period, giving some documentary evidence of just how widely the format spread before a commercial infrastructure existed to contain it.

The second is a default block setting the tempo (in beats per minute), the default note duration, and the default octave.

What RTTTL left behind

RTTTL was eventually superseded by polyphonic formats — Yamaha's SMAF for Japanese i-mode handsets, General MIDI-based sequencing for European devices — and the rise of truetones made the entire synthesised-melody tier commercially marginal by the mid-2000s. But the format never disappeared. Open-source hobbyist communities continued to write RTTTL parsers, and microcontroller enthusiasts adopted it for driving piezo buzzers on Arduino boards decades after Nokia had moved on. A specification designed to fit a melody into an SMS had, almost by accident, become one of the more durable minor file formats in consumer electronics history.