Diablo 1 Save File Location May 2026

Launch the original Diablo 1. Create a new character (name them "TEST"). Quit the game. Now open Windows Search and search for *.sv. Windows will scan every hard drive. Sort by "Date Modified" to find the newly created file instantly.

If you are playing the original disc version, the save files are stored directly inside the game's installation folder.

If installed to C:\Diablo\, the saves remain there. If installed via GOG.com (classic version), GOG uses the same method: saves are in the game’s install directory.

The game saves are stored in the same folder as the game executable (DIABLO.EXE).

Typical paths:

Save files:

⚠️ Note: The game writes saves directly to its install folder, which may cause issues on modern Windows (permissions). Run as admin or install outside Program Files.

If you purchased the game from Good Old Games (GOG), the saves are usually located in your user profile folder:

Once you find the folder, you will see several file types. Here is the cheat sheet:

| File Name Pattern | Purpose | Importance | | :--- | :--- | :--- | | single_0.sv | Single Player Slot 1 | Critical – Your main character. | | single_1.sv | Single Player Slot 2 | Moderate | | multi_0.drv | Multiplayer (IPX/TCP) Slot 1 | Moderate (for LAN parties) | | diablo.ini | Game settings (Resolution, Gamma) | Low | | command.txt | Text log of chat/game commands | Low |

Note: There are no "auto-backups." If your save corrupts, it is gone forever. Always copy single_0.sv to your Desktop before editing with third-party tools.

If you are playing the version provided through the Blizzard App:

  • Modern GOG/Windows 10+ installs (if using compatibility/portable mode):

  • Wine / Linux (including Proton):

  • macOS (classic or via Wine/PortingKit):

    • Common file types

    Notes

    Example path (Windows 10, default install):
C:\Program Files (x86)\Diablo\Save\DefaultUser\CHAR_NAME.CHR

    Related search suggestions added.

    The year was 1999. The air in my bedroom was thick with the smell of burnt pizza rolls and the electric hum of a CRT monitor. I was twelve, and for the last three months, I had been living a second life in the cathedral-shadowed town of Tristram.

    My warrior, Sir Alaric the Bold, was not just a collection of pixels. He was me. He had started with a chipped short sword and a leather cap. Now, he wielded The Boneslayer, a unique great axe that hummed with a vengeance against the undead. He had faced the Skeleton King, Leoric, in the labyrinth beneath the cathedral, and had emerged victorious, his ears still ringing with the king’s cursed laughter. He had even made it to the Caves, level 11, where the very air seemed to bleed.

    One humid July evening, disaster struck. A lightning storm crackled outside. The lights flickered. My family’s clunky Windows 98 machine, a beige tower we called “The Beast,” groaned. And then—a sudden, absolute silence. Then a blue screen. A white text. A fatal exception error.

    My heart stopped.

    I rebooted. The familiar chord of Windows startup played, but my soul was elsewhere. I double-clicked the Diablo icon. The loading screen—that ominous, burning image of the Lord of Terror—flickered. I clicked “Single Player.” I clicked “Load Game.”

    Empty.

    The save slot was a void. A gray, mocking abyss.

    “No,” I whispered. “No, no, no.”

    Three months. The Boneslayer. A ring of the Zodiac I’d found off a dead Goatman. Gone. I felt a grief that was utterly ridiculous and completely real. My father, hearing my strangled cry, came in. “What’s wrong? Did you break the computer?”

    “It’s worse,” I said, my voice cracking. “Diablo ate my warrior.”

    He sighed, the way only a dad who didn’t understand video games could sigh. But he was a logical man. A man of files and folders. He sat down at the keyboard. “Where does the game save the character?” diablo 1 save file location

    I shrugged. I had never thought about it. The game just knew.

    He clicked open “My Computer.” Then “C: Drive.” Then a folder called “Program Files.” Then “Diablo.” We scrolled through the files: DIABAT.MPQ, DIABDAT.MPQ, a few .EXE files. Nothing obvious. No “Saves” folder.

    “Maybe it’s in a hidden directory,” he muttered. He was a genius.

    He navigated up a level. Then he clicked on a folder I’d always ignored: Windows. Inside that, a dusty, cobwebbed digital attic: Profiles. Then my username. Then a subfolder with a strange name: Application Data.

    And there, buried like a secret treasure chest under a floorboard, was a new folder.

    *\Diablo*

    My father clicked it.

    Inside was a single, beautiful, terrifying file:

    Single_0.sv

    “That’s him,” I breathed.

    It was a tiny file. 51 kilobytes. And yet, it contained every decision, every kill, every piece of gold, every desperate potion-chugging moment of Sir Alaric’s existence. The file’s timestamp was from three hours ago—just before the storm.

    The blue screen had corrupted the game’s memory, but the file itself… it was still there. Untouched. The game just couldn’t see it anymore because its internal list had been scrambled.

    “Can we fix it?” I asked.

    He shrugged again, but this time with a spark of challenge. “We can try.” Launch the original Diablo 1

    He copied the file to the desktop. Then, he closed the game, reopened it, and created a new, dummy character named “TEST.” He saved TEST, quit the game, went back to the Application Data\Diablo folder, and replaced the new Single_0.sv with the old one.

    I held my breath as he restarted Diablo.

    Click. Single Player. Load Game.

    And there he was. Sir Alaric the Bold. Level 27. Strength 110. Holding The Boneslayer, standing in the lobby of the Caves, level 11, right where the lightning had found him.

    I screamed. A pure, triumphant, twelve-year-old scream.

    From that day on, I became the guardian of that file. I learned that on Windows 95/98/ME, the sacred path was: C:\Windows\Profiles\[YourName]\Application Data\Diablo\

    On later systems, like Windows 2000 or XP, it migrated to: C:\Documents and Settings\[YourName]\Application Data\Diablo\

    And on modern Windows, it hides in the labyrinth of: C:\Users\[YourName]\AppData\Roaming\Diablo\

    That small, humble .sv file—short for “Save”—was more than data. It was a coffin for the Skeleton King. It was a map to Lazarus. It was a promise that even when the power failed, even when the blue screen came, the journey didn’t have to end.

    I learned to back it up. To copy it onto floppy disks, and later, USB drives. I sent it to a friend across the country so he could play my warrior when I was asleep. We learned that renaming it to Single_1.sv or Single_2.sv would let you have multiple heroes—a feature the game itself never officially explained.

    Twenty-five years later, I still have that file. I’ve copied it across a dozen hard drives, three operating systems, and two continents. I can’t run the original Diablo on my modern PC without a source port or a virtual machine, but the file remains. A 51-kilobyte ghost.

    And sometimes, late at night, I’ll fire up an old emulator, navigate to that hidden, dusty folder in AppData, and load Single_0.sv. Sir Alaric will appear, still gripping his axe, still standing in the dark of the Caves.

    The Butcher still whispers, “Fresh meat.” The acid-spitting dogs still lurk. And my twelve-year-old self is still there, brave and reckless, proving that the greatest treasure in the world isn’t a unique item or a level 15 spell.

    It’s knowing exactly where your save file lives. If installed to C:\Diablo\ , the saves remain there