Quake on PS1 Homebrew: quake-psx, Demo Disc, and Hardware Gotchas

Quake on PS1 took three decades to reach the finish line

A PlayStation version of Quake existed internally during the 1990s, but it never reached store shelves. That left a strange hole in the console’s history: Sony’s machine had the 3D hardware to make the idea plausible, yet players never got an official disc. Modern homebrew has finally filled that gap, though the two prominent routes to PS1 Quake are very different projects with very different compromises.

The practical recommendation here is still straightforward. quake-psx is the build I would choose for emulation, CD-R use, and serious PS1 tinkering. It is a native port of Quake 1.06 Shareware, written in Rust with the PSoXide SDK and purpose-built around the original PlayStation’s 2 MB of main RAM. The PSoXide Demo Disc is easier to sample in a browser, where Quake sits in a carousel alongside other homebrew projects, but it uses substantial AI assistance in its development and asset-cooking workflow, including Claude for debugging and development aid.

That distinction matters less as a philosophical purity test than as an engineering and preservation question. A dedicated, inspectable port with a conventional PS1 BIN/CUE release is a much stronger foundation for future fixes, controller work, full-game support, and community forks. The Demo Disc proves that Quake can run on the hardware. quake-psx gives the project somewhere useful to go.

It also helps that quake-psx is clear about what it is shipping right now. This is Quake 1.06 Shareware rebuilt for original PlayStation hardware, not a vague “inspired by” experiment and not a modern remaster squeezed into a retro shell. That kind of specificity matters when you are dealing with a platform as fussy as the PS1, where the difference between a neat browser demo and a genuinely usable disc image is the whole story.

Where Quake Plus 3D fits, and where it does not

Quake Plus 3D causes unnecessary confusion in PS1 discussions. It is a PC-side Quake engine and resource-mod line associated with enhanced content, including material related to Dissolution of Eternity. It is not a PlayStation homebrew build, and it is not packaged as a native PS1 BIN/CUE release.

Its relevance is expectation management. A PC setup using Quake Plus 3D resources can deliver expanded or enhanced content that current PS1 homebrew does not ship ready-made. quake-psx comes with the 1.06 shareware episode. Its cooker can build a full-game disc from a legitimate PC installation, but that route still requires editing Rust source and working with the PSoXide build process. A simpler workflow that points the cooker at a Steam installation was planned, rather than available as a finished one-click tool.

That means Quake Plus 3D belongs in this conversation mostly as a reminder of what the PC side can do with far more headroom. If you come in expecting expansion content, polished enhancement mods, or a frictionless full-game installer on day one, you are bringing the wrong set of expectations to PS1 homebrew. Right now the PlayStation story is about a convincing native conversion under brutal limits, not about feature parity with the best modern desktop ways to play Quake.

Quake on PS1 options at a glance

Option	What it is	Content at launch	AI involvement	Best use
quake-psx	Native Rust port built with PSoXide for original PS1 hardware	Quake 1.06 Shareware, including the first episode	No substantial AI-dependent pipeline	Emulation, CD-R hardware play, future modding and development
PSoXide Demo Disc	Multi-title PS1 homebrew compilation with Quake in its carousel	Shareware Quake demo entry	Substantial AI assistance in development and asset processing	Fast browser-based sampling and homebrew showcase use
Quake Plus 3D	PC engine/resource mod line	PC-oriented enhanced and expanded Quake material	Not a PS1 port option	Enhanced PC play, not PlayStation hardware

That table is the short version, but one detail deserves to be underlined: only two entries here are even trying to solve the same problem. quake-psx and the PSoXide Demo Disc are both routes to Quake on PlayStation hardware or PS1-oriented emulation. Quake Plus 3D is a separate branch of the family tree. It shapes expectations for “enhanced Quake,” but it does not compete for the same disc tray.

Why quake-psx is the PS1 port I would pick

quake-psx arrived on 25 August 2026 as a roughly 10 MB package containing a standard BIN/CUE disc image. That mundane detail is important. BIN/CUE remains the language real PS1 hardware, DuckStation, and PCSX-Redux understand. There is no emulator running inside the console and no modern system hiding behind the curtain; the game code runs directly on Sony’s original hardware.

The original PlayStation gives it very little room to breathe: a 33.8688 MHz MIPS R3000A-compatible CPU, 2 MB of main RAM, 1 MB of VRAM, and 512 KB of sound RAM. PC Quake was already a demanding 3D game in 1996. Squeezing its binary space partitioned levels, or BSP levels, plus textures, enemy data, sound, and save structures into this machine requires aggressive pre-processing. quake-psx uses an asset cooker to arrange that data for the console’s memory and disc-streaming limits before the game ever boots.

That matters because “native port” is not just a marketing phrase here. It means the work is happening at the level that retro enthusiasts usually care about most: how to make Quake live within the PS1 rather than merely resemble it from a distance. On a machine with only 2 MB of main RAM, every texture decision, every audio compromise, and every streaming trick is part of the adaptation. That is why quake-psx feels more substantial than a proof of concept. It is solving the right problem.

The visual trade-off is unavoidable. PS1 hardware relies on affine texture mapping rather than perspective-correct texturing, which is the technical reason floors and walls appear to wobble or warp as the camera moves. Lower-resolution assets, reduced draw distance, and visible geometric compromises are part of the deal. Those quirks are not a bug in the port; they are the price of putting Quake through hardware built for a radically different era of 3D rendering.

Performance expectations also need restraint. Neither current project provides a formal suite of real-hardware frame-time or frame-rate measurements. What can be said safely is that this is still PS1 Quake: impressive as a technical achievement, comfortably removed from modern 60 fps standards, and best appreciated as a period-style conversion rather than a replacement for a smooth PC build. The hardware budget alone tells you how much compromise is in play before the first shotgun blast.

The other advantage is simply focus. quake-psx is one project with one obvious job. The release is built around getting Quake onto the PlayStation in a form the community can inspect, run, burn, and eventually extend. Even its limitations are productive limitations. Shipping shareware first makes sense on a platform this constrained, and the documented path toward a full commercial build, while still technical, points toward growth instead of one-off spectacle.

Shareware out of the box is a feature and a limitation

It is worth being explicit about what you are getting the moment you download quake-psx. The default release is Quake 1.06 Shareware, which means the first episode and its associated content, not the full retail game with everything unlocked and neatly wrapped for a memory card. That is enough to make the port real, playable, and historically interesting. It is not the same thing as getting the entire commercial package prebuilt for Sony hardware.

There is a route beyond that. The project’s cooker already supports building the full non-shareware game in theory, but right now that remains a hands-on path for technically inclined users who are comfortable modifying Rust source and feeding the tool data from a legitimate PC installation. That makes quake-psx more exciting for tinkerers than for anyone hoping for a frictionless all-in-one retail-style image.

Still, even that roughness has a useful honesty to it. The port is not pretending the hard part is done when it is not. On old hardware, clear limits beat fuzzy promises every time.

The PSoXide Demo Disc is convenient, but it is not the endpoint

The Demo Disc earns credit for accessibility. Its browser version lets someone boot into a WebAssembly-based PS1 emulator and browse a full homebrew carousel without burning a disc, configuring a BIOS, or opening an old console. For a first look, that friction-free approach has real value.

It also creates two easy misunderstandings. Browser smoothness reflects the modern computer emulating a PS1, not the behavior of an aging optical drive and original console. And the Demo Disc is a compilation: Quake shares space with other projects, making its disc layout less focused than a dedicated quake-psx image. A multi-title carousel is fun to browse, but it is not the same thing as a release built around one game’s needs.

That difference in disc philosophy matters more on PS1 than it does on modern systems. The original console uses a 2x-speed CD-ROM drive with a tiny buffer by modern standards, so loading and streaming choices become visible quickly. A dedicated image can be laid out around one set of assets and one set of access patterns. A demo compilation has to serve several masters. That does not make the Demo Disc bad; it makes it a showcase first and a destination second.

The AI-assisted process is the larger reason I would still lean toward quake-psx. AI tools can accelerate debugging or help process an enormous pile of old-format game data, but a retro port deserves a clear technical lineage. For enthusiasts who care about how a game was transformed for a 2 MB console, a conventional source-driven project is more valuable than a cooked demonstration built with substantial generative assistance. That preference does not prove the Demo Disc is less stable or slower; there is no comparable real-hardware benchmark suite to settle that. It does make quake-psx the more compelling project to preserve and extend.

Put more bluntly: the Demo Disc is the one I would show someone for five minutes in a browser tab. quake-psx is the one I would keep if I were building a real PS1 homebrew shelf.

PS1 Mouse support: useful precedent, no current guarantee

Mouse support would make a major difference to how Quake feels on a PlayStation. The official PlayStation Mouse proved long ago that first-person controls can land much closer to the PC experience than a D-pad or early analog setup. Faster turning, more natural aiming, and less reliance on shoulder-button strafing all matter in a game built around quick target tracking.

That said, players should not buy a PlayStation Mouse specifically for quake-psx yet. The port’s public documentation does not advertise native mouse input, dedicated sensitivity options, or bespoke analog tuning. For now, the safe expectation is standard PlayStation controller input rather than a mouse-ready console version of Quake.

This is one of those buyer-level checks that sounds boring until it saves you money. “PS1 supports a mouse” and “this specific homebrew build supports the mouse” are not the same sentence. Treat the mouse as a promising peripheral precedent, not as a guaranteed feature list bullet for the current release. If future forks add it, great. Right now, assume pad controls unless the project itself says otherwise.

Real PS1 hardware is the hardest part of the project

Emulation is the cleanest route. Load the CUE file in DuckStation or PCSX-Redux, use a virtual memory card if you want one, and remove the optical drive from the equation. This is also the best way to establish whether an issue comes from the game image, the emulator configuration, or a physical console that is simply tired after decades of disc duty.

Real hardware is where the romance and the inconvenience meet. Running quake-psx on an original gray PlayStation, a PSOne, or a modified PS2 in PS1 mode means dealing with whatever boot path your machine supports for homebrew media. That may involve a modded console, a pre-existing setup for burned discs, or a more ambitious hardware upgrade. The point is less which route you pick than making sure the route exists before you assume a BIN/CUE automatically equals couch play.

The original PS1 drive itself is part of the equation. Sony’s hardware was built around a 2x CD-ROM mechanism, and no amount of enthusiasm changes the fact that many surviving units are now old, inconsistent, or picky about media. If your console already struggles with burned discs or long loads in ordinary PS1 software, a homebrew Quake port is not going to be the forgiving test case that fixes your luck.

That is why the obvious advice still matters. Use decent CD-R media. Burn conservatively rather than chasing speed. Expect some setups to be fussier than others. And remember that a browser demo or an emulator session tells you almost nothing about the health of a thirty-year-old laser assembly. The hardware ceiling here is not just CPU and RAM. It is also the reality that physical PS1 play depends on a drive subsystem from another century.

An XStation SD-card optical-drive emulator is the cleaner long-term escape hatch if your console is compatible and you are comfortable with the installation requirements. Listings have put it around $51 through AliExpress sellers. The important part is not the exact storefront price but what the device changes: it replaces disc-reading with solid-state storage, which removes CD-R quality and failing-laser variables from the process. It is a hardware upgrade, not a magic memory card, and buyers need to verify motherboard compatibility before they click anything.

The same caution applies to any “easy fix” language around boot methods. Homebrew on original PlayStation hardware is doable, but it is never completely abstract. Some friction is the hobby.

Memory cards need a little caution too

A standard PS1 memory card holds 128 KB, commonly treated as 15 usable blocks with system management overhead taking the rest. quake-psx does not document its precise save-block requirement here, so there is no reason to treat an almost-full card as “probably fine” and discover otherwise after a long session. If you plan to save, a clean and dependable card is the sensible starting point.

That caution is less dramatic than the disc-drive talk, but it is more common in practice. Old memory cards fail. Third-party cards can behave strangely. A card that has been carrying the same RPG and sports saves since the early 2000s may not be the card you want to trust with fresh homebrew experiments. If you are taking the original-hardware route seriously, keeping one known-good card for homebrew use is the tidy, low-stress move.

Modern alternatives like PSXMemCard are appealing precisely because they sidestep the old ritual of juggling blocks across aging 128 KB cards. They can be useful for collectors who want cleaner save management across multiple projects. What they do not do is solve boot failures, fix bad burns, or tell you anything about a specific port’s undocumented save footprint. A fancy storage solution cannot compensate for uncertainty somewhere else in the chain.

That is the broader rule for PS1 Quake right now. Keep the storage side boring. Keep the boot path simple. Keep your expectations tied to the actual release in front of you, not to the best-case scenario in your head.

The real appeal is not perfection, it is legitimacy

There is an easy mistake to make with projects like this, which is to judge them against the smoothest, cleanest, most feature-rich modern version of Quake and stop there. If that is the test, the PS1 loses before the logo fades in. But that is also missing the point. The thrill here is not that the original PlayStation suddenly became the ideal Quake machine. It is that the machine finally has a version that feels like it belongs to it.

That is why quake-psx stands out. It respects the PS1 as a specific piece of hardware with severe, interesting limitations. It ships in the format that hardware expects. It starts from shareware and points toward more. It is technically legible in a way that makes preservation, future fixes, and community experimentation feel plausible rather than decorative.

The PSoXide Demo Disc still has a place. It is a good front door, a neat showcase, and an effective way to let people see Quake running under a PlayStation-flavored wrapper without asking them to do any retro surgery. But if the question is which route feels like a project with a future, not just a cool party trick, the answer does not get more complicated the longer I stare at it.

PS1 Quake took an absurdly long time to become real. Now that it is here, the version worth following is the one that behaves like an actual port, not merely a clever demonstration that the idea can survive contact with the hardware.