i built this because at some point you start noticing a pattern
things that were genuinely good… slowly become worse. small devs ship something great, a company buys it, optimizes it into oblivion, and suddenly you're left wondering how a simple tool turned into a "what happened here?" story. CCleaner is basically a case study at this point, everyone knows, nobody needs another paragraph about it
funny enough, CCleaner only ever really survived because of the community around it, especially things like the winapp2.ini signatures. that ecosystem did more for the tool than most official decisions ever did.
i was too lazy to rebuild all cleaners natively, so i just wrote a parser for that format instead. turns out its fast. like… surprisingly fast. faster than what i remember from the old piriform implementation (no idea why that was so slow, proprietary formats, overengineering, or just history doing its thing. doesnt matter anymore anyway)
the UI is built in WinUI3 you know, Microsofts "beautiful but slow" framework, except somehow it still manages to outperform the original. go figure
companies today dont really compete on making things better. they compete on who can add more noise without breaking everything completely. and somewhere along the way, "good tools" just turned into "things people remember fondly"
CCleaner used to be great. now it’s mostly a warning.
anyway, im not trying to fix the indutry. just wanted something that doesnt suck. i'll probably get bored, or it'll evolve into something else, and we end up back at square one like always.
for now i just called it FluentCleaner.
it wasnt even meant to be public, but a lot of genuinely nice people asked me to release it, so i probably will here's a first preview so you can get a feel for the direction. i might end up funding it through donations, we'll see.
if you like it, cool. if not, also fair
will this make my PC faster?
honestly? it depends and that's not a cop-out
on a modern system with plenty of free space, you probably won't notice a dramatic speed boost. but Microsoft themselves say that running low on storage can slow things down and even block Windows updates (source) so if your drive is getting full, cleaning matters more than you'd think.
beyond speed, there are solid reasons to clean regularly:
- reclaim disk space that's been quietly eaten up over months
- troubleshoot app issues caused by corrupted cache
- shrink backup size
- privacy, browser data, recently opened file lists, leftover traces from apps you uninstalled
- keep Windows updates running smoothly
- or just because a tidy system feels better. also valid.
Microsoft recommends doing this monthly. Storage Sense does it automatically. FluentCleaner just gives you more control over what exactly gets cleaned
what even is winapp2.ini?
a community-maintained database of cleaning rules for Windows apps, thousands of entries built up over 15+ years. it tells FluentCleaner exactly what to clean for each app: which temp folders, which cache paths, which registry keys. no guessing, no sweeping wildcards across your whole drive. every entry is specific, inspectable, and auditable. that's the whole point.
what are flavors?
winapp2.ini comes in different variants depending on which tool you're using. FluentCleaner uses the original CCleaner flavor, the same one that powered the tool back when it was still worth using
is it safe?
it's as safe as what you enable. nothing runs without you selecting it first. winapp2.ini entries only target what they're explicitly told to target, no broad "delete everything in temp" nonsense. that said: it deletes files. take a backup if something feels important
why WinUI 3?
because it's 2026 and windows tools shouldn't look like they were built in 2009. also fluent design is literally in the name. felt right
CCleaner 7 dropped winapp2.ini support, what does that mean for FluentCleaner?
nothing. FluentCleaner has its own parser, completely independent of CCleaner CCleaner dropping support was honestly part of the motivation to build this
can i use a custom winapp2 database?
yes. FluentCleaner isn't locked to one source.
tools like BBleachBit (primarily a Linux cleaner, discovered it through this project actually, but the UI was bad enough that it came right back off), and others have their own flavors of winapp2.ini, slightly modified versions tuned for their specific needs. you can grab any of them (or build your own) and plug it straight into FluentCleaner.
just drop the file somewhere on your system, then head to: Settings > Database > Custom and point it at your file. that's it.
the official database from the winapp2 project lives here: https://github.com/MoscaDotTo/Winapp2, it's community-maintained, updated regularly, and covers thousands of apps. a solid starting point if you want more coverage than the default.
source code?
coming. still figuring out the license. for now: preview binary, open feedback.