Windows · Updated 2026-11-03
Bloodborne on Windows: three community routes
Sony has not released Bloodborne for Windows. Three community builds do run the PS4 game on Windows, and since 28 October 2026 the original project ships its own Windows build instead of leaving Windows to forks. Each route has its own launcher, online server and update rhythm.
What the three builds are
The original deadinside28 project, usually called bbport, is a community runtime that runs the game's x86-64 executable with replacement system libraries and a Vulkan backend. Release 0.7 on 28 October 2026 was its first native Windows build, published next to the Linux packages.
Supermedo's Bloodborne for Windows is a separate Windows port with its own launcher, settings, update mechanism and online service. Mrsuss60's project is another independent Windows tree that tracks upstream bbport work. None of them is a Sony release, and none includes the game.
Because the three projects share a family tree but not a codebase, a fix, a save or an online account from one is not automatically valid in another.
Route comparison
Read down the column that matches your hardware and what you want from online play. The requirements below are the maintainers' published minimums, not measured performance.
| Route | Latest checked | Published requirements | Online | Frame and upscaler options |
|---|---|---|---|---|
| bbport (deadinside28) | 0.7, 28 Oct 2026 | Windows 10/11, x86-64, Vulkan 1.3 | Seamless Hunt (account + BBSC) or The Hunter's Dream (Discord) | FSR 3.1, FSR 4, FSR 4.1.x; DLSS and DLSS Frame Generation through a bridge |
| Supermedo | windows-v1.9.7, 30 Oct 2026 | Windows 10 1903+ or 11, AVX and BMI1/MOVBE/LZCNT, Vulkan 1.3, about 6 GB free RAM plus page file | SuperMedo Server only; The Hunter's Dream removed in 1.9.7 | 30/60/90/120 cap, DLSS on RTX 20+, FSR 3.1/4, AMD ML-FG on supported RX 9000 |
| Mrsuss60 | v0.8.0, 1 Nov 2026 | Windows 10/11 64-bit, Vulkan 1.3, GTX 10-series / RX 400-series / Arc A-series, AVX1 + SSE4.2 (AVX2 not required) | Follow that release's notes; not a shared server with the other two | 30/60/90/uncapped, FSR upscaling, asynchronous pipeline compilation |
The install boundary is the same on all three
Every route expects a complete game folder you are permitted to use, with update 1.09 and a clean eboot.bin; the projects document CUSA03173. Owning a disc is not by itself a licence to copy or bypass protection in every jurisdiction, and this site does not provide game files, firmware, bypass tools or mirror links.
Install each build into its own empty folder and keep saves backed up before switching. Mixing files from two Windows builds is a common way to get a launcher that starts and then fails, and the projects' own troubleshooting sections assume their own file layout.
Expect weekly version churn
All three projects shipped several releases in the week before this check: Supermedo went from 1.9.4 to 1.9.7 between 21 and 30 October, Mrsuss60 from 0.6.5 to 0.8.0 between 21 October and 1 November, and bbport from 0.6 to 0.7 on 28 October. A guide that names a version without a date is not a reliable guide.
Prefer the tagged release page over a repository's default branch. When a launcher offers to update itself, read that release's note first: Supermedo's 1.9.6 to 1.9.7 step, for example, changed which online server the port uses and removed The Hunter's Dream.
Questions
Is there an official Bloodborne Windows version?
No. The publisher sources checked list a PlayStation 4 release playable on PS5 by backward compatibility. All Windows builds described here are community projects.
Which Windows build should I start with?
There is no single best build. The original bbport 0.7 is the project that added native Windows support in October 2026; Supermedo has the most guided launcher and its own server; Mrsuss60 tracks upstream work with its own 30/60/90/uncapped options. Match the release to your GPU, then follow that release's instructions only.
Can players on different builds play together?
That was not verified. Supermedo now runs on SuperMedo Server, while bbport 0.7 documents its own two pools. Treat cross-build sessions as unsupported unless the projects say otherwise.