What an achievement actually is
A Steam achievement is a named flag stored against your account for a specific game. The developer defines the list, and while you play, the game calls the Steam API to set a flag when you meet its condition. Steam stores the flag and the moment it was set, then shows it on your profile and in the game's achievement page.
Everything happens on the game's side. Steam does not verify that you killed the boss or finished the level; it receives an instruction that says "mark this achievement unlocked for this user" and it does so. The platform has no independent record of what you did to deserve it.
Earning versus unlocking
This design is why third-party unlocking tools exist. Anything that can talk to the Steam API as your account can set the same flags the game would set, in any order, at any time. Once written, the achievement is indistinguishable in the stored data from one earned by playing — the record contains the achievement name, the account and the timestamp, and nothing about how it got there.
The practical result is that achievement completion on Steam is not evidence of anything. A perfect 100% on a notoriously difficult game can be genuine or can be a few seconds of API calls, and the profile displays both identically.
Why instant unlocking looks obvious anyway
The timestamps are the giveaway. Steam records when each achievement was unlocked and displays that publicly, and it also shows your recorded playtime for the game. Forty achievements sharing the same minute on an account with twelve minutes of playtime tells the whole story to anyone who opens the page. Completionist tracking sites are built on exactly this data, and several of them flag or exclude profiles with implausible unlock patterns.
There is also the global rarity display. Steam shows the percentage of owners who have each achievement, so an account holding a 0.3% achievement alongside a 90% one it unlocked eleven seconds later is visibly inconsistent with normal play.
What drip unlocking does differently
Drip unlocking spreads the same set of achievements across a stretch of real time while the game is reported as running. Instead of everything landing at once, achievements appear at intervals, in an order that follows the game's progression, against playtime that actually exists on the account.
The result reads far more naturally: the profile shows a game with plausible hours and achievements distributed across them, which is what a real playthrough produces. It is slower by design — you are trading immediacy for a history that holds up to a glance. Boostr's achievement feature offers both modes, and it pairs with idling because the playtime and the unlocks accrue together.
Being honest about detectability
Nothing here is invisible. Valve can see the API calls, developers can query their own achievement statistics, and anyone browsing your profile can read the timestamps. Some developers have publicly reset achievements on accounts they judged to have used unlockers, and community leaderboards and completionist sites remove profiles for the same reason.
Using third-party software to interact with Steam is also against the subscriber agreement, the same as idling. Achievement unlocking is not covered by VAC — that is per-game anti-cheat and it is not running here — but administrative action by Valve remains possible in principle. Realistically the more common outcomes are a developer reset, an exclusion from a tracking site, or nothing at all.
Things worth knowing before you start
A few practical points that come up repeatedly.
- Achievements have no effect on your Steam level or XP — that comes from crafted badges only.
- Locking achievements again is possible for most games, but the reset does not always propagate to third-party trackers.
- A few games store progress server-side and will re-lock or overwrite achievements when you next launch them.
- Games with no achievement list cannot be unlocked at all; check the store page first.
- Unlock timestamps are public. If that matters to you, drip unlocking is the only sensible mode.