What you end up with
Uncage running in your browser, on your own computer. It is free, and it stays free — there is no account, no trial and no subscription at the end of this.
- Time
- About 28 minutes
- Steps
- 11
- Cost
- Free
Before you start
These are one-time installs. If you have used PowerShell before, you may have them already — the first step checks.
Install Git
Run the installer, then reopen PowerShell.
Open installerYou know this worked when: Git responds with a version number
Install Node LTS
Run the LTS installer, then reopen PowerShell.
Open downloadYou know this worked when: Node responds with a version number
Install Uncage
Open PowerShell
Keep it open beside this page.
You know this worked when: PowerShell is open
Check Git and Node
Git and the current Node LTS are required.
Type this into PowerShell, then press Enter.
git --version node --versionYou know this worked when: Git and Node respond with version numbers
Copy Uncage to this PC
Type this into PowerShell, then press Enter.
cd ~ if [ ! -d uncage/.git ]; then git clone https://github.com/Nightteye/uncage.git fiYou know this worked when: A uncage folder appears
Open the Uncage folder
Type this into PowerShell, then press Enter.
cd uncageYou know this worked when: Your terminal prompt is inside the uncage folder
Use the reviewed version
Type this into PowerShell, then press Enter.
git checkout 39f14b2e325941e39853fc6c87136d707564291bYou know this worked when: Git reports the reviewed commit
Install dependencies
Type this into PowerShell, then press Enter.
npm.cmd installYou know this worked when: The command finishes without an error
Run Uncage
Keep PowerShell open.
Type this into PowerShell, then press Enter.
npm.cmd run startYou know this worked when: localhost:3000 responds
Open it in your browser
If a different port was picked, open that one instead.
Open localhost:3000You know this worked when: The app loads in the browser
Try it
Uncage should be open in your browser.
You know this worked when: Uncage works
If something goes wrong
Nothing here can damage your computer, and every step can be run again safely. If a command fails, the usual cause is the step before it not having finished.
Still stuck? Tell us what happened and we will fix the guide. Include the step number and we can usually reproduce it.