Red
Lead Dev · Owner
Runs the whole R3D operation. The vision, the direction, and the hands on nearly every part of it.
// about
This thing turns your osu! replay into a video. Drop the
.osr in Discord, or upload it on the
upload page, and you get a share link back with the render. No replay file? Paste an osu! score link instead. All four modes.
By mode
Most-rendered players
Why it exists
I built it because I wanted it to exist. It runs on my hardware, in my apartment. It's free, because that's the point of a personal project you like enough to keep running. No ads, and no telemetry beyond what the pipeline needs.
How it works
Discord is the easier path. Drop a replay in a channel the bot's in and it posts back with an inline video and a permalink. Everyone in the server benefits, with no per-user setup. The web upload does the same thing with a progress bar and a settings panel, handy when you want to override the skin, drop the watermark, or submit a batch of plays at once.
All four modes render on our own engines. std, taiko, catch and mania all sit on the same foundation, each pixel-faithful to lazer's Argon. Everything runs in-house, top to bottom.
Free & supporter
I'm not monetising this. Supporters just cover the hardware. View supporter details in account settings.
When renders fail
Renders sometimes fail. If the beatmap can't be resolved or a codec chokes, the job stops and tells you what happened instead of shipping the wrong output. Failed renders open bug reports automatically. If something else breaks, hit report on any render page. Takedowns go through /dmca, and feedback goes on the forum, or straight to me on Discord (RedWolfie) or at [email protected].
Source code
The source for the engine behind every render on this site is public. Each mode's renderer lives on GitHub — read it, build it, or run your own.
Everything R3D publishes is at github.com/R3dWolfie.
Core team
Runs the whole R3D operation. The vision, the direction, and the hands on nearly every part of it.
The backbone the whole thing stands on. The foundation every renderer is built from, and the reason it all runs.
Works on the core engine behind every render, and builds and shapes the site you're looking at right now.
Builds the core engine and render pipeline with Red, signs off every engine release before it goes out, works on the contributor app, and made the tracker the whole team plans its work in.
On the catch renderer with the team — chasing down the details that make it feel exactly like the game.
Building new features and polishing the site with Green.
Gets the renders in front of people — runs the socials and the YouTube side.
The renderers wouldn't be what they are without these communities.
Cato The Beat · Discord
For mastering the catch renderer with us, and the endless troubleshooting that got it right.
UK Taiko · Discord
For helping perfect the taiko renderer, down to the details only players would notice.
Skin makers · osu! community
Every skin people render with was made by someone in the community. Thank you.
Where it started
We didn't invent the wheel. Rendering osu! replays to video was already a thing, and R3D is built on the idea and approach of the projects below. We just made our own.
Built on
osu! and every beatmap this renders belong to ppy and the community. R3D just puts the replays on video.