RuneScape came out on January 4, 2001, when brothers Andrew and Paul Gower opened their browser-based game, then called RuneScape, to the public after a short friends-and-family test. It ran directly in Java inside a web page with no download, a decision that shaped who could play it and why it scaled the way it did. That date marks the original release, not the 2004 launch of RuneScape 2 or the 2013 launch of Old School RuneScape.
Launch mechanics: why January 4, 2001 was the release date
The Gowers built the game on a Java applet platform rather than a downloaded client. A player loaded a web page, the applet streamed the game world from a server, and the roster of players in one shared space became the technical bottleneck. Andrew Gower had previously run the DeviousMUD experiments, and the RuneScape name was carried into the public launch.
The public opening followed a limited test phase, so the January 4 date reflects the switch from private testing to open access. The game launched as a free-to-play experience supported by ads and a small server footprint. That structure matters because the release date people cite is the moment of public availability, not the moment the code existed.
Browser delivery lowered the entry barrier in 2001. A school computer or a low-end home PC with a Java-enabled browser could run it. That constraint pushed design toward tile-based movement, a fixed isometric camera, and server-authoritative combat resolution rather than client-side physics.
One counterintuitive detail: the earliest release ran on servers that could hold a few hundred players at once, far below what modern players imagine. The whole early game was engineered around those ceilings. One plain sentence: the game was small by necessity, and that smallness is why it spread.
Quantified context: dates, scope, and version counts
The chronology is more layered than a single date suggests. The original RuneScape, often called RuneScape Classic today, opened on January 4, 2001. RuneScape 2, a full engine rewrite on a new codebase, launched in March 2004. Old School RuneScape, a fork built from a 2007 backup, launched in February 2013.
The game world grew in bounded steps. The original map covered a modest landmass. Membership, introduced in 2002, added a paid tier with additional content and a monthly fee. That membership model funded server expansion and larger development staff without changing the browser-based access model.
The engine rewrite is where the numbers get interesting. RuneScape 2 replaced the original tile rendering and combat systems, raising the visual and mechanical ceiling. Old School RuneScape then froze the game at a 2007-era snapshot and grew it separately through player-voted content. Three live versions of one game lineage means the phrase "when did RuneScape come out" depends on which lineage you mean.
Production scale rose over the years, but the precise current headcounts and revenue figures are not something this article asserts without a specific source. What remains stable is the ordering: a 2001 browser applet, a 2004 rewrite, and a 2013 preservation fork.
Version timeline
| Version | Launch date | Engine | Core change |
|---|---|---|---|
| RuneScape Classic (original) | January 4, 2001 | Java applet, tile-based | Public browser launch |
| Membership tier added | 2002 | Same engine | Paid content and monthly subscription |
| RuneScape 2 | March 2004 | New engine | Rewritten rendering and combat |
| Old School RuneScape | February 2013 | 2007-era snapshot | Player-voted content branches |
| Modern RuneScape updates | Ongoing | RuneScape 2 lineage | Continuous live-service updates |
The table makes the hidden structure obvious. There was never a single launch. There was a lineage with two forks, and each fork has its own "release" moment.
Edge cases: what people actually mean by the release date
The most common edge case is the game's name confusion. RuneScape and RuneScape Classic are often used interchangeably for the 2001 product, but Classic was retroactively named. Players who say "when did RuneScape come out" sometimes mean the 2004 version because that is when the game they remember appeared.
A second edge case is regional availability. Browser access broadened reach, but performance depended on Java support, server proximity, and connection quality. Players in different regions experienced very different latency, which shaped which activities were practical.
A third edge case is account migration. Original accounts did not automatically carry every benefit into the rewritten game, and Old School RuneScape required separate progression. The migration rules are a frequent source of confusion for returning players.
Red flags worth noting: Do not cite a single "release date" without naming the version; the dates differ by years. Do not assume a 2001 account grants access to the 2004 game or to Old School RuneScape. Do not treat the January 4 date as the date of the engine rewrite; that was March 2004. Do not assume the browser applet still runs on modern browsers; Java applet support has been removed from major browsers.
Misconceptions: the 2004 rewrite and the applet myth
The biggest misconception is that RuneScape 2 was a patch. It was a rewrite. The team replaced the original rendering and combat systems rather than extending them. That is why Classic was retired and why the two games feel mechanically different despite sharing a name.
The second misconception is that browser games cannot scale. The early RuneScape proves the opposite. A Java applet combined with server-side world partitioning let the game serve large numbers of players at a fraction of the hardware cost of a downloaded client. The ceiling was per-world player counts, not global reach.
A third misconception is that Classic was shut down because it failed. It was retired because maintaining an old engine alongside a new one split development and server resources. The cost of dual maintenance, not player rejection, drove the decision. One plain sentence: keeping two engines alive was more expensive than the old game was worth to the company.
The professional caveat is that release dates in live-service games are defined by uptime and public access, not by version control tags. A game can "launch" repeatedly as new platforms and versions appear. This article's dates describe public access per version, not code commits.
Practical actions: how to pin down the date you need
If you need the release date for research or a citation, use a decision sequence.
Name the version first: original 2001 game, 2004 rewrite, or 2013 Old School fork. For the original, cite January 4, 2001 as the public launch date. For the rewrite, cite March 2004 as the RuneScape 2 game launch. For Old School, cite February 2013 as the fork launch. Check whether your source uses "RuneScape Classic" as a retroactive label before quoting a date. If a source gives a single date without naming the version, treat it as ambiguous.
A simple threshold rule helps. If the game you are describing had tile-based movement and the original combat system, you mean the 2001 release. If it had the rewritten visuals and combat, you mean 2004. If it had a 2007-era content snapshot and player voting, you mean 2013.
The comparison table below applies the same logic to related alternatives, so you can see where the dates sit relative to other browser-era games.
| Game | Public release | Delivery model | Notable structural feature |
|---|---|---|---|
| RuneScape (original) | January 4, 2001 | Java applet in browser | Shared persistent world |
| RuneScape 2 | March 2004 | Browser client | Rewritten engine |
| Old School RuneScape | February 2013 | Browser and client | Player-voted content |
| RuneScape Classic retirement | 2018 | N/A | Historical archive status |
Limitations: what the record cannot settle
The historical record is strong on major dates and weaker on exact test-phase timing. The January 4, 2001 date is the accepted public launch, but the precise duration and roster size of the pre-launch test are not something this article asserts without a specific source. Treat any precise test-phase claim as needing verification.
Server capacities and player counts at launch are also hard to pin. Early hardware and network limits are known in kind but not in exact figures here. What is stable is that the ceilings existed and shaped the design. The game's tile-based movement and server-authoritative combat are direct consequences of those constraints.
The current landscape adds another limit. Version status, player numbers, and monetization change constantly. This article deliberately avoids dated operational figures because they would age within weeks. The stable mechanism is the browser-based, server-partitioned design, and that mechanism has not changed even as the game's versions have multiplied.
For any use that depends on a precise date for a specific version, confirm against the version's own launch announcement rather than a secondary summary. The conservative answer is always to name the version before quoting the date. The Gower brothers' browser game came out on January 4, 2001, and every later date is a fork of that same lineage.