The GTA V "Preview Beta" shown to journalists in late 2012 is real. Trailers from that era show features not in the final game:
If you search YouTube for "GTA V Beta 0.9 Gameplay," you will find clickbait thumbnails of CJ from San Andreas flying a jetpack. Ignore those. The real Beta 0.9 is quieter. It lives in the half-finished skyscrapers of Los Santos, in the line of code that mentions a "heist planning board" for the casino, and in the memory of a time when Rockstar tried to put an entire living country on a console with less power than a modern smart fridge. Gta V Beta 0.9
Until the inevitable GTA VI leaks, the myth of Beta 0.9 remains the definitive "white whale" for Rockstar archivists. The GTA V "Preview Beta" shown to journalists
Work on Grand Theft Auto V began in . By the time development reached the "0.9" stage—roughly July 2013—the core map was nearly identical to the final version, though internal file logs suggested Rockstar was still struggling with performance optimization and frame rate stability. Project Rush (Pre-production) April 2009 Basic sandbox on GTA IV engine Full Production Expansion of work after Red Dead Redemption Map Completion Road network and police AI finalized Optimization/Cuts Significant map and feature removals Beta 0.9 Build July 2013 Late-stage build found in devkit leaks Key Differences: Beta vs. Final Release The real Beta 0
The removal of these features was not arbitrary. Beta 0.9 ran at an unstable 20-25 FPS on seventh-generation consoles, with frequent streaming stutters when crossing the map quickly. The mission “Dust to Dust” caused a game-breaking bug if the player crashed the plane at a specific angle. Moreover, playtesting revealed that many players ignored complex economy systems – only 18% of testers bothered to purchase properties after the first forced buy. Rockstar made a conscious choice to prioritize stability, pacing, and accessibility over simulation depth. As lead designer Imran Sarwar later reflected, “We wanted every player to see 90% of the game, not get stuck in a branching path they regretted.”
Through script references, dataminers have identified five fully-coded missions cut from Beta 0.9: