How to Start Speedrunning Browser Games

Speedrunning browser games has a lower bar than console speedrunning by a wide margin. No capture card, no emulator config, no specialized hardware. You need a browser, free recording software, and a willingness to do the same level fifty times in a row. This guide walks through the actual steps from “I want to try this” to “I have a verified submission on speedrun.com.”

Step 1: Pick a game and a category

The first decision is which game to run. The friendliest entry points for browser-game speedrunning are games with existing leaderboards, clear categories, and active communities. Good starting picks include the Chrome Dino game (score-based categories), 2048 (fastest to a target tile), Cookie Clicker (first prestige and similar milestone runs), and Universal Paperclips (any%, since it has a defined ending).

Open speedrun.com, search the game’s name, and look at the category list. Each category has its own rules — what counts as the start, what counts as the end, what tools and settings are allowed. Read these carefully. The number-one reason a submission gets rejected is using an off-spec game version or starting the timer in the wrong place.

Step 2: Watch the top runs before you practice

This is the step new speedrunners skip and regret. Before grinding attempts, watch the current top three to five runs on the category leaderboard. Watch them at full speed first, then again at half-speed if the game supports it. Pay attention to:

• The exact moment the runner starts the timer.
• The route they take through the game — which choices, which order, which skipped sections.
• Tricks or strategies that don’t seem intuitive.
• What they do when something goes wrong — the reset criteria.

Routing is the single biggest factor in early speedrun improvement. A new runner who has watched the routes carefully and plays them at half-speed will beat a more reflex-skilled runner who’s improvising. Reflex training comes later; the route is the multiplier.

Step 3: Set up OBS Studio

OBS Studio is the standard recording tool for speedrunners. It’s free, cross-platform, and produces files speedrun.com will accept. Download from obsproject.com, install, and open the application.

The minimum setup for browser-game recording:

• Scene: Add a “Display Capture” source pointing to your monitor, or “Window Capture” pointing to your browser specifically.
• Audio: Capture desktop audio (the game’s sounds) and optionally your microphone for commentary.
• Output: Set the recording format to MP4. Speedrun.com accepts most common formats but MP4 is the safe default.
• Frame rate: 60fps is standard. Anything lower can cause verification issues on faster games.

Run a test recording before your real runs. Record yourself starting a fresh game, do a quick attempt, and stop. Play back the file and check that the audio and video synced correctly. Most submission rejections in this category come from missing audio (the timer beep is inaudible) or dropped frames.

Step 4: Get a timer

Most browser-game speedruns use in-game time when the game provides it, and external timing when it doesn’t. For external timing, LiveSplit (Windows) is the standard tool. Free, configurable per-game, integrates with OBS as a video overlay. On Mac and Linux, splitterino or web-based timers are common alternatives.

Configure your timer’s splits before your first practice run. A split is a checkpoint within the run — usually a milestone like “first prestige” in Cookie Clicker or “first 100 points” in Chrome Dino. The splits help you identify which sections of the run you’re losing time in. Don’t worry about gold-splitting initially; just set them up so you can see your section times.

Step 5: Run the route until it’s muscle memory

This is the grinding phase. The first hundred attempts at a route feel slow and clumsy. The next hundred feel marginally less so. Around attempt three hundred, the route starts feeling like one continuous motion instead of a sequence of discrete decisions. That transition is the real speedrun skill, and it can’t be shortcut.

A few habits that help:

• Reset early. If a run starts badly, restart immediately rather than playing it out. You’re optimizing learning, not playing for fun.
• Note one improvement at a time. Trying to fix three things at once usually produces worse runs. Pick the biggest time loss and focus on that.
• Track your PB and golds. Personal best is your fastest complete run; gold splits are your fastest segment times. Both are useful — golds tell you what’s theoretically possible if you stitch your best segments together.
• Stop when you’re tired. Speedrunning while exhausted produces sloppy runs and bad habits. Most runners cap sessions at one to two hours.

Step 6: Talk to the community before submitting

Every game with a leaderboard has a forum on speedrun.com and usually a Discord. Before submitting your first run, post a message in the appropriate channel introducing yourself and confirming category rules. The veterans almost always help. They’ve watched dozens of new runners make the same mistakes — wrong start point, wrong game version, missing audio track — and they’ll tell you about them before verification rejects you.

This step costs nothing and saves hours of frustration. Speedrunning communities are some of the most welcoming corners of the internet to newcomers willing to ask questions.

Step 7: Submit your run

When you have a run you’re proud of, submit it. On speedrun.com, log in, navigate to the game’s category page, and click “Submit run.” You’ll be asked for the video link, the time, the platform, and any category-specific fields. Upload the video to YouTube or Twitch first; speedrun.com doesn’t host video, it just links to it.

The submission goes into a verification queue. Verification can take hours or weeks depending on the game’s moderator activity. While you wait, keep practicing — submitting one run is meaningful, but the goal is to have multiple submissions over time as you improve.

Common beginner mistakes

• Not reading the category rules. Skipping this is the single biggest cause of rejected runs.
• Recording at low frame rate or with the in-game audio muted. Both can disqualify an otherwise valid run.
• Submitting a single best-attempt video without a clear timer. Most categories require a visible timer overlay or a recognized in-game timer.
• Comparing yourself to world-record holders. WR holders have thousands of hours of practice. Your first goal is the leaderboard’s bottom third, not the top.
• Quitting after a few weeks. Improvement is non-linear. Most runners hit a wall at 50–100 hours and break through it at 200.

Which browser games to start with

Cookie Clicker first-prestige is one of the friendliest beginner categories — runs are five to ten minutes, the route is documented exhaustively in community guides, and the leaderboard is welcoming to all skill levels. 2048 to-2048 is another good starting point: short runs, deterministic-with-known-randomness, well-defined rules.

If you want a reflex-based starting point rather than a strategy one, the Chrome Dino game’s score categories work — runs are short, the obstacle patterns repeat, and the practice loop is tight. Just be aware that the Chrome Dino categories have unusual rules about which version of the game counts (the official Chrome version, the open-source mirror, third-party recreations — each has slightly different validation criteria, so read the leaderboard notes carefully).

The longer arc

Speedrunning is a long hobby. Most runners take six to twelve months to reach the top half of their first leaderboard, and another year to reach top-ten in any meaningful category. The reward isn’t the rank — it’s the focused practice and the community that develops around a shared goal. For more on how the browser-speedrunning scene grew into what it is now, our history of browser-game speedrunning covers the milestones.

Frequently asked questions

Do I need a capture card to speedrun browser games?

No. Browser games run on the same computer you’re recording with, so screen-capture via OBS works fine. Capture cards are only needed when the game runs on separate hardware (console, handheld).

How long until I can submit my first run?

For shorter browser-game categories, most newcomers can submit a competitive run within 10–20 hours of practice. The submission doesn’t need to be world-record — the leaderboard tracks all verified runs.

What software do I need to start?

OBS Studio for recording (free), LiveSplit or an equivalent for timing (free), and a YouTube or Twitch account for uploading the video. That’s it. No paid tools are required.

Can I speedrun on a Chromebook?

Yes, but it’s harder. OBS Studio doesn’t run natively on ChromeOS — you’d need to use a web-based screen recorder or run OBS through the Linux container. Most Chromebook speedrunners record on a separate machine.

Is speedrunning browser games considered “real” speedrunning?

Yes. Speedrun.com verifies browser-game runs to the same standard as console runs, and AGDQ has featured browser games in its marathon lineup. The scene is smaller than console speedrunning but the standards are the same.

Where to go from here

Pick a game, watch the top three runs on its speedrun.com leaderboard, set up OBS, and start grinding. The first dozen attempts will feel awkward; that’s the universal experience. Submit when you’re proud of a run, not when you’ve matched the world record. The community will meet you where you are. The lowest-friction starting point is right here — open the Chrome Dino game, start the timer, and see how the first run feels.