
Game Overview
A doomed cargo freighter drifts through deep space with five people aboard, dwindling supplies, and no realistic prospect of rescue. Mouthwashing turns that simple survival setup into a suffocating first-person psychological horror story, where the damaged ship feels almost as hostile as the people trapped inside it. Captain Curly survives the crash in a grotesquely helpless state, leaving the remaining crew to confront the consequences of a catastrophe that may not be accidental. The tone is relentlessly bleak, mixing isolation, resentment, guilt, and surreal terror rather than relying on constant monster chases.
Players move through the Tulpar’s cramped corridors, examine objects, follow conversations, and complete small environmental tasks while the narrative jumps between key moments before and after the wreck. Exploration is deliberately focused instead of open-ended: details in medical bays, cargo areas, crew quarters, and malfunctioning systems gradually reveal what happened and how badly each survivor is coping. There is no conventional combat system or resource-management simulation, so tension comes from restricted movement, disturbing imagery, unreliable perception, and the knowledge that food and power are running out. Progress depends on paying attention to dialogue, visual clues, and shifts in perspective, with several sequences turning familiar spaces into feverish nightmare versions of themselves.
Its strongest feature is the way it makes the crew’s personal failures feel inseparable from the horror surrounding them. Low-poly character models and deliberately rough, retro-inspired visuals give the game an uncanny, dreamlike quality, while sharp writing keeps the interpersonal cruelty painfully grounded. The story is compact but dense, encouraging a second playthrough to catch foreshadowing and reinterpret earlier scenes once its central revelations land. Fans of SOMA, Signalis, and narrative-heavy indie horror should find plenty to admire, especially if they prefer unsettling character drama over action-heavy scares; newcomers to horror can finish it, but should expect disturbing themes and little emotional relief.
Screenshots
Installation
- Select the Download button at the top of this page to open UploadHaven.
- On UploadHaven, wait for any countdown, then select Free Download. Optional: UploadHaven Pro for faster downloads.
- When complete, extract the archive to a Mouthwashing folder using 7-Zip.
- Open the extracted folder and start the game normally.
- For errors, check Setup Guide & Troubleshooting below. Keep your security software enabled.
System Requirements
- OS *: Windows 7 64-bit
- Processor: i5-6300HQ
- Memory: 8 GB RAM
- Graphics: GTX 560
- DirectX: Version 11
- Storage: 3 GB available space
Setup Guide & Troubleshooting
How do I fix missing DLL errors for Mouthwashing (v2025.09.22)?
After extracting Mouthwashing (v2025.09.22), navigate to the _Redist or _CommonRedist folder inside the game directory and install DirectX, Vcredist, and any other dependencies included.
What should I do if the downloaded file is corrupted?
The full archive is 1.44 GB — make sure your download completed fully before extracting. Use 7-Zip to extract the files. If you still see a "file corrupted" error, re-download and try again.
Do I need to run the game as administrator?
Usually, no. Start the game normally from the extracted folder. If you see a permissions or save error, check that the folder is writable and follow the game's documented fix. Only grant administrator access when a trusted game's specific setup requires it.
How do I update my GPU drivers for this game?
The game won't launch — what should I try?
Check that extraction completed and your PC meets the system requirements, including Version 11. Note any error message before choosing a fix. If it identifies a missing runtime, install the required DirectX components or Microsoft Visual C++ Redistributable from Microsoft.
My antivirus is blocking the game — is it safe?
A warning needs to be investigated; the download source alone cannot confirm that a file is safe. Keep your security software enabled and review the detection details. Do not run or restore a flagged file unless you have verified that it is a false positive. If you are unsure, leave it quarantined.