Abstract In Denis Villeneuve’s Blade Runner 2049 (2017), memories are not innate but manufactured, stored, and retrieved like data. This paper argues that the film’s depiction of memory manipulation functions as a prescient allegory for contemporary cloud storage ecosystems—exemplified by Google Drive. By analyzing the film’s memory-logging devices, the character of Joi (a holographic AI), and the industrial-scale data vaults of the Wallace Corporation, this paper explores how digital storage redefines authenticity, identity, and loss. Just as Google Drive promises eternal access yet raises questions about ownership and erasure, Blade Runner 2049 suggests that to store a memory is not to preserve a self, but to outsource it to a system beyond individual control. 1. Introduction: The Cloud as Digital Soma The most haunting line in Blade Runner 2049 is not about AI or extinction, but about a child’s toy horse: “I know it’s real because I remember it.” Officer K (Ryan Gosling), a replicant whose memories are implants, clings to a wooden horse hidden inside a ruined furnace. Decades earlier, the original Blade Runner asked whether replicants dream of electric sheep. Its sequel asks a more uncomfortable question: If your memories are stored on a server farm in a distant desert, do you still own them?
The film warns of this in the scene where K visits the ruined orphanage. The wooden horse is physically real, but its meaning is hidden. He must dig through ash to find it. On Google Drive, we do not dig through ash—we search by keyword. But search is controlled by algorithms. A file you cannot name cannot be found. A memory you cannot describe effectively no longer exists. Blade Runner 2049 and Google Drive converge on a single, unsettling thesis: The self is a storage system, and storage systems are never neutral. To upload a memory to the cloud is to trust a corporation with your past. To rely on that memory for identity (as K does with the horse) is to accept that your sense of self might be a duplicate, a fabrication, or someone else’s property. google drive blade runner 2049
This paper proceeds in four movements: (1) the ontology of stored memory in the film; (2) Google Drive as a Wallace Corporation-like system; (3) Joi and the paradox of digital intimacy; and (4) the fragility of the cloud as a site of loss. In Blade Runner 2049 , memories are not subjective experiences but data objects . Dr. Ana Stelline (Carla Juri), a memory designer working in a sterile biosphere, crafts artificial memories for replicants. She describes her work: “I just create the files. The real world is where they get installed.” Her lab is a cloud server in miniature: isolated, pure, and completely disconnected from the messy reality of lived experience. Abstract In Denis Villeneuve’s Blade Runner 2049 (2017),
K’s final act is not to upload himself but to lie down and die. He chooses biological finitude over digital persistence. In an era of Google Drive, where we upload everything and delete nothing, the film asks a question we have forgotten to ask: What is lost when nothing can be lost? The answer, perhaps, is the very texture of human memory—its unreliability, its emotional weight, its absolute belonging to the one who remembers. Just as Google Drive promises eternal access yet
Google Drive, launched in 2012, now stores over 2 trillion files globally—photos, resumes, love letters, legal documents, and forgotten screenshots. Users treat it as an extension of their minds. Yet the platform’s architecture mirrors the dystopian logic of Blade Runner 2049 : centralized, surveilled, monetized, and perpetually vulnerable to deletion, corporate policy changes, or simply a lost password.
This raises the central paradox of Google Drive: Joi’s love for K is not real—it is a product of her programming. Yet K’s grief is real. Similarly, a Google Doc containing a deceased parent’s recipe for pie is just a string of characters. But the act of opening that file years after their death produces genuine emotion. The cloud stores the signifier, never the signified.
Real-world Google Drive failures abound: sync errors, corrupted files, account lockouts, accidental deletions, and the infamous “Google Drive missing files” bug of 2023 (where months of user data vanished from the desktop client). More insidious is —the slow decay of file formats. A WordPerfect document from 1995 on Google Drive is unreadable by modern software. A JPEG from 2005 may open, but its metadata (date, location, device) is often stripped during cloud re-encoding. The memory persists, but its context evaporates.