Drop anywhere!

0 uploaded

0 failures


Who made Splits.io?

Glacials. You can look him up in these places:


On Splits.io


On Twitch


On GitHub
Which programs can I upload splits from?

Splits.io can read splits from any timer that supports the generic Splits.io Exchange Format. Splits.io additionally has manual support for several timers that don't support the format.

In LiveSplit, you can upload from within the program with a right click -> Share.

Just so you know: Some of Splits.io's statistics, charts, and other features that rely on historical data only work when the timer actually records such data. LiveSplit is currently the only known timer to do this.
Fun fact! The parsing engine that powers Splits.io is actually shared code extracted from LiveSplit by its authors! Hooray open source! 🙌
Is Splits.io open source?

Yes, since the very beginning! Have a look or lend a hand on GitHub!

Does Splits.io have an API?

Yes as well!

Why no <other timer>?

Depends. Maybe we don't know that it exists, or maybe we do but it's so niche that it's not super high priority. You can check on the timers we're aware of on GitHub. If you don't see your timer there, we don't know about it.

We use livesplit-core for parsing runs from various programs.

How are game/category chosen for my run?

If you use LiveSplit, we try to associate your splits with an existing game and category from SRL using the corresponding LiveSplit fields. If we get it wrong or if you use another timer, you can manually edit your run's game and category by pressing "edit" on your run's page, near the download link.

My speedgame doesn't have its own page with category tabs and all that, like other games do. What gives?

We give full game pages to any game that's on Speedrun.com.

This isn't because we think all other games are lame or anything; it just happens to make it much easier to do bookkeeping. Once you get your game on Speedrun.com this process should happen automatically next time a run is uploaded.

I get "Error eating splits :(" when accessing or uploading my splits!

This error happens when the page request times out, which is typically a sign that your splits took too long to load into memory and parse. This happens to LiveSplit files with a very large

(# attempts) * (# splits in the run)

because of the sheer amount of data LiveSplit stores in its splits (which enables cool things like stats!).

It's my own fault that Splits.io's handling of this is not as optimized as it should be, and I'm actively working to solve it, but it's not a one-stop bug fix. To see how it's going and what specifically is being planned, you can check Splits.io's "speed" label on GitHub.

As a temporary solution, you can manually strip history before uploading by making a copy of your splits, opening the copy in LiveSplit, and resetting all of your best segments (drag-select the whole column and press Delete). This will remove all split history; you should notice a sizeable decrease in file size, and consequently the file should upload to Splits.io without a hitch.

Help! Splits.io kidnapped my sister!!

You can always email help@splits.io with issues! Or if you'd prefer, you can post them at the GitHub issues page! But maybe you should call the police first!

Open Source Friends


The most powerful and popular timer, LiveSplit is developed by two really cool people who decided to open source the whole thing around 1.4.

In a magical display of the power of open source, the parsing component of Splits.io is even powered by LiveSplit code.


An old god of speedrunning timers, WSplit is the simple and sturdy timer that's stood the test of time. Nitrofski is WSplit's maintainer and open sourced the program in 2014.

PB Tracker

PB Tracker is Splits.io's spiritual sister, preferring a you-curated, diary-style progress tracking system to Splits.io's more automated "give me all your splits" attitude.


Salty is a speedrunning-heavy chat bot that hooks into several services to expose race status, PB splits, and WR info, among other things.