Takes out the junk
Advertising ID. Telemetry. Copilot. Widgets. Bing wedged into your Start menu. The suggested apps you have never once opened. All of it, gone.
Free · open source · nothing to install
Debloat Windows
without breaking it.
Trim rips out the ads, telemetry and preinstalled junk, then tunes what’s left for games. You see the whole list before anything happens. Hate the result? One file puts every setting back.
irm https://trimbloat.com/go | iex
Paste that into PowerShell. Windows will ask for admin rights. A window opens, and nothing on your PC changes until you say so.
- 60things to change on a typical PC
- 1file that undoes every one
- 0things installed on your system
What it does
Five jobs.
It tells you exactly what it plans to do in each one, and waits for you to agree.
Sets it up for games
Game Bar off. Background recording off. Windowed games get the fast path. Every game it finds gets pointed at your real GPU instead of the integrated one. On NVIDIA it also applies a driver profile composed for your exact card.
Finds the wasted space
It checks every drive, not just C:. Update leftovers, crash dumps, shader caches, the recycle bins you forgot about. You see the size of each pile and where it lives before any of it goes.
Uninstalls things properly
Most uninstallers leave a mess. Trim runs the app’s own uninstaller, then goes looking for the folders, registry keys, services and scheduled tasks it abandoned. You approve each one — services and tasks are never ticked for you — and anything it found but will not touch is named rather than hidden.
Shows what starts with Windows
Every program that launches when you sign in — the Run keys, both Startup folders and logon scheduled tasks. Switch off a Run entry and it uses the same switch Task Manager does, so it stays off and you can turn it back on without this tool. A Startup folder shortcut gets moved rather than deleted. Scheduled tasks are listed so you can see them, not changed.
The actual app
Here’s what you get.
The real window, rendered by the app itself — no mockups. The machine it describes is a stand-in: publishing our own would publish a motherboard, disk models, drive labels, installed games and startup programs, which is nobody else’s business.
It explains itself in plain English, then prints a full spec sheet of your machine. On the PC that generated this, it found 60 things worth changing and 39 already set the way it would set them.
Every row shows the setting, what it is now, and what it would become. Untick anything you disagree with. Only the SAFE ones are ticked when it opens.
Thirteen categories, scanned across every drive you have. Each one shows its size and where it is, so you are never agreeing to delete something described only as “temporary files”.
Each entry says who published it and where it is configured, which Task Manager does not. Shortcuts are moved rather than deleted, and the undo script puts them back. A scheduled task shows as one instead of offering a button it could not honour.
Remove an app, then look at what it left behind. Folders, registry keys, the service that no longer has a binary, the update task that still runs. Nothing goes without you seeing it, and nothing it declines to touch goes unmentioned.
How it works
Run it. Read it. Apply it.
You can stop after step two and nothing will have happened.
-
1
Run one line
Nothing is installed and nothing is left running. It writes its log, its ledger and its undo script to
C:\ProgramData\Trim, and puts a copy of itself in your temp folder when it needs admin rights — because handing an elevated shell a file it can check beats re-downloading one it cannot. Windows asks for those rights because these settings genuinely need them, and you should be wary of anything that claims otherwise. -
2
Read the list
It scans your PC and shows what it would change, labelled by risk. Untick what you do not want. Close the window and your machine is exactly as you left it.
-
3
Apply, or undo
Click Apply and it makes the changes you kept. It asks Windows for a restore point first — and tells you if Windows refuses, which happens where System Protection is off by policy. An undo script lands in
C:\ProgramData\Trim\undoand reverses every setting it wrote, bar the three exceptions below.
Is it safe?
Check it yourself.
You do not have to take our word for any of this. Three ways to verify what you are about to run, in about a minute.
01 Read it
It is served as plain text, not a download. Open it in a tab and read the whole thing — one file, nothing minified or obfuscated. What it fetches while it runs is somebody else’s code: WinUtil, if you keep that phase; NVIDIA Profile Inspector, if you have the card; and Chris Titus Tech’s PowerShell profile, if you tick it. All three are named below, and you can read the lines that go and get them.
Open the script02 Check the fingerprint
Every build publishes its SHA256. Run it with -Version and it
prints the fingerprint of the file sitting on your machine.
451C057D00C9A432EE78D808A389C7C2D5D58FDF4FCB31E1D36970A8292D0FFC
View /sha25603 Build it yourself
A published hash proves the file reached you intact. Reproducibility proves it matches the source. Build the commit it was built from and you get byte-identical output.
git clone https://github.com/Glexxy/trim
cd trim
git checkout <commit>
.\build.ps1The commit is on line 4 of the script itself —
# Source: commit … — because the head of the repository
may have moved since this build was published, and then the hashes would not
match and nothing would tell you why. Same commit, same fingerprint. Very few
tools distributed this way can be checked that far.
What it refuses to touch
- Your camera and mic. Those, plus screenshots and screen recording, are on a never-touch list checked while it runs. A typo cannot switch off your webcam.
- Fan curves, BIOS, overclocking. Nothing here can cook your hardware, because none of it goes anywhere near that.
- AutoLogon. WinUtil offers it. It writes your password somewhere anything on the machine can read, so Trim leaves it alone.
- Anything load-bearing. Shared runtimes, winget, the Xbox sign-in service. Remove those and games start failing in ways that look nothing like a debloat problem.
- Guesswork about your PC. Laptop or desktop, NVIDIA or AMD or Intel, SSD or spinning disk. It checks first and skips what does not apply.
- You. No analytics, no account, no telemetry of its own. It talks to two hosts and no others: this site, for the script, its fingerprint and its tweak list; and GitHub for three things — WinUtil if you keep that phase and NVIDIA Profile Inspector if you have the card, each pinned to one release and one SHA256, and Chris Titus Tech’s PowerShell profile if you tick it, which is not pinned and is a Caution row for that reason. Read the script and you will find those two hosts and nothing else.
Reversible
Changed your mind?
Every registry write goes through one function, and that function writes down the old value before it touches anything. When the run ends — even if it crashes halfway — that ledger becomes a script.
C:\ProgramData\Trim\undo\undo_<timestamp>.ps1Three things it genuinely cannot take back, said up front:
Store apps it removed (reinstall them from the Store), WinUtil’s own
changes (that is what the restore point is for), and netsh TCP
settings (one command, printed in the log).
-
A value that never existed gets deleted
Not set to zero. Getting that one case wrong is why so many “restore” scripts quietly leave your machine different from how they found it.
-
A restore point goes first
Before the plan is applied, so you can roll back the whole machine and not just the settings Trim happens to know about. Where System Protection is switched off by policy Windows refuses, and the run says so on screen instead of leaving you to assume otherwise.
-
The round trip is tested
Apply, roll back, then check every value came back to its exact previous state and type. Including the awkward ones nobody tests, like multi-strings.
Questions
Fair questions.
Is it actually free?
Yes. MIT licensed, open source, no paid tier, no account, nothing to buy later. There is no business model here to be suspicious of.
Will it break my PC?
That is the thing it is built to avoid. Only the changes marked SAFE are ticked when it opens, a restore point is taken before the plan is applied unless Windows refuses to make one, and every registry change is written down so it can be put back exactly. It also stays away from the things that actually kill machines: BIOS, fan curves, overclocking, and the Windows components other software depends on.
Does it work on Windows 10?
Yes, 10 and 11. It works out which one you are on and skips whatever does not apply to your build.
Do I have to install anything?
No. It runs from PowerShell and leaves no program behind. It does write
files: its log, its ledger and the undo script, all three in
C:\ProgramData\Trim, plus a copy of itself in your temp folder
when it needs admin rights — because handing an elevated shell a file it
can check beats re-downloading one it cannot.
Why does it want admin rights?
Because half of what it changes is machine-wide: scheduled tasks,
services, and registry keys under HKEY_LOCAL_MACHINE — several of which
cannot even be read without it, which is why the one-liner asks once at the
start rather than mid-run. Nothing is changed until you say so — the plan
waits for Apply, and the Startup, Cleanup and Uninstall panes each ask first. If you
would rather grant nothing at all, -DryRun runs unelevated and
prints the plan; it says so at the top, because the handful of values it
cannot read are missing from it.
Will it give me more FPS?
Sometimes a bit. Often nothing you would notice. Killing background telemetry and pointing games at the right GPU does real work on a cluttered laptop and almost nothing on a clean, well-specced desktop. Anyone promising you a specific frame-rate gain from registry edits is guessing or lying.
Can I undo it weeks later?
Yes. The undo script is an ordinary file with a timestamp in its name. It sits there until you delete it, and it works whenever you run it.
How is this different from WinUtil?
Trim uses WinUtil for one of its twelve phases — the tweak set Chris Titus Tech already maintains, which there is no sense reimplementing. The rest is Trim's own: the dry run you can read, the recorded undo path, hardware detection, disk cleanup, the deep uninstall, the startup manager, the NVIDIA profile and a risk label on every change. They solve different problems; WinUtil is a broad Windows toolbox, Trim is a reversible clean-up with a plan you approve first.
Go and look at your own PC.
Windows asks for admin, a window opens, and nothing changes until you say so. Worst case you close it, having found out what Windows has been up to.
irm https://trimbloat.com/go | iex