Is bbport an emulator?

No. The PS4's CPU is already x86-64, so bbport runs Bloodborne's original code directly on the PC's CPU with no CPU emulation or per-instruction translation. A small runtime written for Bloodborne replaces the PS4 system libraries. Only graphics still need translation, from PS4 GPU commands and shaders to Vulkan. It supports Bloodborne and nothing else.

Which version of Bloodborne does bbport support?

Only version 1.09 (the project targets CUSA03173). You need your own game data; the project ships no game files.

Does bbport work on Windows and Steam Deck?

The original bbport targets x86-64 Linux and offers a Steam Deck AppImage. On Windows there is a fork maintained by Supermedo. It does not run directly on ARM devices such as phones or Macs.

bbport or shadPS4 for Bloodborne?

bbport only does Bloodborne, with lower CPU overhead, higher frame rates and in-game upscaler and graphics settings. shadPS4 is a general emulator that runs many games and is already mature in Bloodborne (Digital Foundry measured 4K60). bbport's graphics side itself started from shadPS4.

Will Sony take bbport down?

As of November 1, 2026, GitHub's public DMCA repository has no Sony notice against bbport or similar ports, and Sony has not commented. In January 2025 Sony did file a DMCA against the page for a Bloodborne 60 fps patch; Push Square reported it was about the use of the Bloodborne trademark.

What is bbport? The native Bloodborne PC port for Linux (Oct 2026)

On October 1, 2026, developer deadinside28 released bbport 0.1, which runs the original PS4 executable of Bloodborne (CUSA03173, version 1.09) directly on an x86-64 Linux PC. The project description is blunt: "It is not a general emulator." The game's own x86-64 code runs as-is on the CPU, a small runtime written for this one game replaces the PS4 system libraries, and GPU work is translated to Vulkan by a renderer derived from shadPS4 and heavily extended for Bloodborne. VGTimes reported about 150 fps at 1440p on an RX 7800 XT. It is still experimental, and no one has verified a full playthrough.

Why "native" is possible

The PS4 uses an AMD x86-64 processor, the same instruction set as a regular PC. Bloodborne's game logic can already execute on a PC CPU. The hard parts are the PS4 system functions it calls (memory, threads, files, audio, controller, saves) and the PS4 GPU. bbport's approach:

CPU: the eboot is converted ahead of time into a native x86-64 image (DSOGaming's description), and a loader jumps straight into the game code. No CPU emulation, no per-instruction translation.
System libraries: only the PS4 functions Bloodborne actually calls are implemented.
Graphics: PS4 GPU commands and shaders are translated to Vulkan, with a renderer and shader recompiler that started from shadPS4's.

Think of it as Wine plus DXVK, built for a single game. Tom's Hardware Italy points out that "native" here describes how the game code runs; rendering still goes through translation.

How it differs from shadPS4

Wccftech reproduced the project's own comparison. The main rows:

	shadPS4	bbport
Scope	General PS4 emulator, many games	Bloodborne 1.09 only
Loading	Its own ELF loader and kernel emulation at run time	eboot converted offline, then a small loader jumps into the game
System libraries	Broad emulation of the PS4 OS	Small runtime with only what Bloodborne calls
GPU thread	One thread handles the whole command stream, Bloodborne's bottleneck	Decode and draw recording on separate threads, scales with hardware threads (Steam Deck included)
Upscaling	None	FSR 3.1, FSR 4, FSR 4.1.1 with the game's own motion vectors and jitter

Performance and features

VGTimes reported the developer's numbers on an RX 7800 XT:

Setting	Frame rate
1440p, FSR 4 Quality	about 150 fps
4K, FSR 4 Balanced	about 90 fps

Early features, per Wccftech and DSOGaming:

unlocked frame rate plus 30, 60 and 90 fps modes;
AMD FSR 3.1, FSR 4 and FSR 4.1.1 temporal upscaling;
an in-game menu for upscaler, preset and output resolution, and toggles for depth of field, motion blur, SSAO and more, no config files to edit;
a launcher, mod support, free camera and a Steam Deck AppImage;
saves, sound and controller work; the developer played the Hunter's Dream and several areas of Yharnam.

DSOGaming's main complaint at launch was the lack of mouse support.

Requirements

an x86-64 Linux PC or a Steam Deck;
a GPU with Vulkan 1.3;
your own Bloodborne game data, updated to 1.09. The project includes no game files.

Windows, and the wave that followed

bbport started on Linux, and a Windows fork came fast: both DSOGaming and TechPowerUp refer to Supermedo's Bloodborne Windows port. Over the next few weeks the same idea was applied to God of War III Remastered, Uncharted: The Nathan Drake Collection, Driveclub, Gran Turismo Sport and more; see October's wave of native PS4 ports. The same month, a developer built on it to bring Bloodborne to Snapdragon Android devices; see Bloodborne-Android.

Where Sony stands

As of November 1, 2026, Sony has said nothing publicly about bbport, and GitHub's DMCA repository shows no Sony notices for September or October 2026. There is one precedent: in January 2025 Sony sent a DMCA notice against the page for Lance McDonald's years-old Bloodborne 60 fps patch. Push Square reported the issue was the page's use of the Bloodborne trademark, not the patch itself.

What this means for players

If you want Bloodborne on a Linux PC or Steam Deck with higher frame rates and in-game graphics options, bbport is the alternative to shadPS4. It only covers this one game and full-game stability is unverified, so shadPS4 remains the fallback if you hit late-game problems. Compare the two on the bbport page, the shadPS4 page and the Bloodborne page.

bbport, the native Bloodborne PC port: no emulator, the PS4 code runs directly on Linux at up to 150 fps

Key points