# PlayStation classics in the browser Source: https://ported2browser.org/platforms/playstation/ A small shelf of console-era favorites, rebuilt through named community projects. ## What PlayStation browser games means in this collection PlayStation browser games can describe several different technical approaches. Some websites emulate console hardware, while other projects recreate or rewrite an engine associated with a game that appeared on the console. This collection currently follows the second route through OpenLara and Phoboslab's WipEout project. The platform label is a discovery aid for people who remember those games from the PlayStation era. It is not a claim that the listed destinations run disc images through a PlayStation emulator or reproduce every console-specific detail. That distinction gives the collection a clear scope. OpenLara's web link is identified upstream as a demo-level WebGL build. The WipEout destination exposes its own full and minimal loading choices. Each project has a named origin, a particular implementation, and its own content boundary. Open the game entry before following the destination so that you know which route you are choosing. Someone wanting an exact memory-card workflow, every regional difference, or compatibility with a personal disc archive should not infer those features from a familiar cover image. The implementation matters as much as the title. ## Revisit the control language of an earlier era Console-era three-dimensional games often express movement differently from contemporary releases. A character may turn and advance through a deliberate scheme, while a racing craft may rely on thrust and separate airbrakes. Start by reading the actual bindings rather than assuming that a modern controller layout will be recognized automatically. Browser controller access, input mapping, and the game's design are separate questions. If you use a gamepad, test every essential action before beginning a difficult section. Keyboard input can provide a useful comparison if a mapping is uncertain. For adventure movement, practice orientation and a safe jump before combining several actions. For racing, establish how steering behaves before adding advanced corrections. The first goal is predictable control. A missed action can result from timing, focus, or an unfamiliar binding, and those causes need different responses. Click the play surface if the page still owns the input, learn how to return to the menu, and keep a way to leave fullscreen. These checks may sound small, but they often determine whether a short nostalgia visit becomes an enjoyable session or an exercise in fighting the browser interface. ## Demo scope and resource choices are part of the experience A demonstration is valuable on its own terms. It can reveal how an engine handles movement, rendering, and input without promising every area of a commercial game. OpenLara's upstream demo label therefore belongs near the destination rather than hidden in a footnote. If you want a complete campaign, investigate the current project instructions and any own-data workflow before making plans. The source availability of an engine does not by itself transfer the distribution rights for levels, music, artwork, or disc content. This directory does not provide commercial game archives. A resource choice can affect a session even when no local file import is needed. Phoboslab's WipEout page distinguishes a larger full option from a smaller minimal option without introduction or music. Check the current figures and decide what suits your connection. A smaller download is not a guarantee of smooth rendering, and an intentionally absent soundtrack is not a browser audio failure. Keeping those categories separate makes troubleshooting much more effective. Read the destination's visible controls and loading labels, give a progressing loader time to finish, and avoid switching builds repeatedly before you have established what each option is meant to do. ## Compare the memory with the actual project Nostalgia can create expectations that a community project never claimed to meet. A particular soundtrack, camera behavior, visual effect, or controller feel may be central to your memory. If one matters to you, investigate it directly rather than treating a familiar opening image as proof. A rewrite can be impressive preservation work while making different implementation choices. The directory identifies those projects so you can appreciate and evaluate them accurately. It does not describe them as official releases, complete remasters, or universal substitutes for every historical edition. For a first visit, choose a small objective such as exploring one room or completing a practice lap. Notice the input, display fit, and audio behavior on your own setup. Do not generalize a single result into universal compatibility. If something looks wrong, compare the current upstream notes before changing several browser settings. Record the exact stage and visible message if a failure repeats. A source review can establish what a project is and what it advertises, but a device-specific observation requires its own date and context. Our launch collection keeps that limit explicit instead of inventing a full playtest history. ## Preserve progress and choose your next step Classic console memories often include a tangible save card, but browser progress may live in local site storage or a project's virtual filesystem. Before relying on a lengthy session, check whether the destination documents persistence, records, or export features. Make a disposable test where possible and preserve an external copy if the interface supports it. Clearing site data or switching profiles can remove access to locally stored progress. A screenshot can record a race result, but it is not a universal replacement for a saved campaign. A directory bookmark only preserves the route back to the page. The browser can be a convenient place to explore these projects, learn about engine preservation, and revisit an old control style. A maintained native release or another documented setup may fit a full campaign or a specific archival goal better. Keep that decision tied to what you want to do. As the collection grows, new entries should be traceable to an upstream author and describe their technical identity honestly. You can submit a project, changed requirement, or broken link with its authoritative source and a date. That helps this shelf of PlayStation browser games remain a useful guide to actual community work rather than a vague promise attached to a recognizable console name. If you remember a game through a particular controller or display, treat that memory as a preference to investigate rather than a compatibility requirement the project automatically meets. Try a small section, note what feels familiar, and identify what differs. This can make revisiting an old title more interesting: you are exploring both the game and a new implementation of it. Share that context when recommending the project. A precise description of a demo or rewrite helps another player appreciate the author's work without expecting an exact disc-era environment that the destination never claimed to recreate. ## Related games - [Tomb Raider]() - [WipEout]()