STOWIT COMPRESS™
Space back from what is already on your disk. 16× smaller, one command, nothing moves. Your apps never notice — same files, same speed. Free forever.
Click below to see how much space you can get
OUR ATTIC™
Need MORE space? Our cloud attic refuses to store anything you can download again — so you keep every model you actually use, without buying a bigger machine.
Click below to run the models you want
no account · nothing leaves your machine · nothing is ever deleted
Products
Your files get smaller. They do not move.
Same folders, same paths, same bytes — fewer blocks on the disk. On a real Mac one node_modules went 374 MB to 222 MB.
Nothing is relocated, so no app can lose track of anything — the paths it opens today are the paths it opens after. Nothing is uploaded, nothing is deleted, and there is no account.
A drive you own, without the hope-then-delete.
Dock copies the heavy stuff across, reads every byte back and checks it against a cryptographic manifest, and only then frees the space here. If the check fails, nothing is removed.
Because dragging is a gamble: the path breaks, the app cannot find its files, and you find out weeks later. Dock leaves a live shortcut at the original path, so the folder still opens as if it never left — and it never frees a byte it has not proved is safely elsewhere.
The only cloud that argues with you about what to store.
Every other cloud is paid by the gigabyte, so none has a reason to tell you that half of what you are uploading already sits on a public server. Attic keeps a receipt instead of the bytes for anything the registry promises never to delete — Go modules, npm packages, Rust crates, NuGet packages — and does not bill you for them.
Most developers fit Basic: 40 GB stored, $6 a month or $49 a year. You only need room for what we actually hold, after Attic has refused everything you could download again. Getting your files back is always free.
It reads the copy back before it believes it. Uploading is not backing up. After Attic sends an object it downloads the whole thing again and decrypts it, and only then does it count — which is why a push moves twice its size. A copy you have not read is not a backup, and no general-purpose cloud checks.
It insures the models that can be taken away from you. A weight file from ollama or HuggingFace has an honest hash and no promise whatsoever about the hosting: models get withdrawn and licences change overnight. Attic keeps a sealed copy of those specifically, because a receipt is worthless once the shelf is empty.
It cannot read your files, and it cannot hold them hostage. Everything is sealed on your machine before it leaves — we hold no key, which is a fact about how it is built rather than a promise about how we behave. A lapsed card never blocks a download, and plain export is free forever. It also works today against storage you already own: a NAS, a share, or your own bucket.
FAQ
stowit proof on the computer.Pricing
Free
Free · you supply the drive
Pick the room you need for what we actually hold — after Attic has refused everything you could download again, and compressed the rest. One real 230Todd’s own 230 GB Mac needed 14.9 GB.nbsp;GB Mac needed 14.9Todd’s own 230 GB Mac needed 14.9 GB.nbsp;GB.
Basic
40 GB · $6 a month or $49 a year
Fits most developer machines we have measured.
Pro
100 GB · $15 a month or $119 a year
A few local models you could not download again.
The Kraken
1,000 GB · $99 a month or $1,079 a year
For the model hoard that will not fit on any laptop.
Why not “unlimited”? Because somebody pays for every byte, and a flat plan charges you the same for your photographs as for a node_modules you could rebuild in ninety seconds. Attic refuses the second kind, so you need far less room than you think.
Restores are free and unmetered. Getting your own data back is not a place to put a meter. Run out of room and new uploads pause; nothing you stored is ever touched.
Install and run stowit proof on the computer holding your files. Read-only — nothing moves until you say so.
What you get
Everything else that frees up a disk does it by throwing your files away. Stowit moves them instead — onto a drive you own — and leaves a shortcut where they used to be, so your projects, your tools and your editor never notice they went anywhere. Ask for a folder back and it comes back. Nothing is ever deleted to make room: Stowit can't free a single byte on your Mac until it has already made a checked copy somewhere else. That isn't a promise on a website — it's the only order the program is able to run in.
Press Show me my number for the install line and
stowit proof — the read-only command that measures your disk for real. This page
does not fill these in.
How it works
Stowit lists what you've stopped using — old project folders, model files, build leftovers — with the size of each one and how long it's been sitting untouched. Nothing moves at this point. You pick.
Everything is copied to your drive first. Then Stowit reads both copies back and compares them file by file. Only once every single one matches does it free the space on your disk.
A shortcut stays behind where the files used to be, so nothing breaks. Ask for them back and they come home in about a second, checked again on the way in.
What it finds
What it deliberately won't touch: the builds you've shipped (Xcode Archives) and your phone backups. Those exist nowhere else, and a moved copy on one drive isn't the same promise as a file that can always be downloaded again.
A folder only counts when the file that proves what it is sits next to it. Something that merely shares a name is never picked up.
Where the space goes
All three end the same way: the files still exist, and you can still open them. All three work today — with the limits each one actually has, said plainly.
Any external drive becomes your vault. Files are copied across, checked one by one against the originals, and only then cleared off your disk. A shortcut stays behind where they were, so nothing you've built notices.
This is the whole product today, and it's free. The code that moves your bytes is open and auditable — only the planner that decides for you is closed.
The heaviest folders compress down to a fraction of their size and stay exactly where they are — same path, still readable, still openable at full speed. No drive, no moving, nothing to plug in.
macOS only — it uses the compression built into the Mac's own filesystem, and there is no equivalent elsewhere yet. On Linux stowit says so rather than pretending.
A second copy somewhere that isn't your vault — a NAS, a network share, another drive. Files are sealed shut on your machine before they leave it, and stowit downloads the copy back and opens it before it will call it verified.
It's a place you already own: point it at your own storage and it works now, including S3-compatible cloud storage on your own account. There is no service of ours to sign up for, and this page won't imply one. A folder on the same disk as your vault is refused — two copies that die together are one copy.
How to use it
Free to use, and open where it counts: the code that moves your bytes is auditable. Every command tells you what it's about to do, and nothing moves a byte until a verified copy exists somewhere else.
brew install toddfishman/tap/stowit
On Windows there is no Homebrew, so:
irm https://stowit.dev/install.ps1 | iex
stowit proof ~/codeStart here. Three numbers — what you'd get back by compressing where things sit, by moving them to a drive, or by sealing them into the cloud. Read-only: it changes nothing.stowit compress-place <path>Space back with nothing moved anywhere — the folder stays exactly where it is and every file still opens at full speed. No drive needed.stowit docker-compactUsually the biggest single thing on a developer's disk. Hands back the space Docker has already finished with — nothing is removed, so there's nothing to confirm — and reports what your disk actually gained.stowit scan ~/codeSee what's reclaimable — every artifact, its size, and how long it's sat untouched.stowit dock <path>Move something out: copied to your drive, checked byte for byte, then — and only then — freed here. A shortcut stays behind.stowit statusWhat's stowed, where it is, and how much space it's giving you back.stowit undock <id>Bring it home — verified again on the way back in.stowit revive <path>Your drive is at home and you are not. Rebuilds the folder and checks every byte against the sealed record before handing it back. If it can't match that record it says so and waits, rather than hand you something nearly right.stowit verifyRe-check every stowed byte against its record, any time you feel like auditing us.stowit attic remote <dir>Point the attic at a second, independent place — a NAS, a network share, another drive. A folder on the same disk as your vault is refused: that is not a second copy.stowit attic push --allSend everything sealed to that place, then download each one again and open it before calling it verified. It moves about twice the size on purpose — a copy you haven't read is not a backup.stowit attic verify-remoteRe-read the off-site copies and check they still open. Run it after a restart, when nothing can be answered from memory.stowit panicThe big red button: restore everything, now.The promise
Most tools that free up space do it by throwing your files away. Stowit moves them instead — and this isn't a promise on a website, it's the shape of the code. The part that frees space on your disk cannot run until a checked copy already exists on your drive. There is no order of operations that loses a file.
Measured on a MacBook Pro with a Samsung T9, 14 August 2026. The last one is a folder of 84,375 files.
Where it runs
Linux is not a promise any more — every command was run on one and the binaries ship. A few things stay Mac-only because they use the Mac's own filesystem (squeezing folders in place, the fast restore), and elsewhere stowit says so instead of quietly doing nothing.
Windows arrived in v0.5.5, and it is a download rather than a promise. The shortcut it leaves behind is a Windows junction, which needs no special permissions. Two honest caveats: the binary isn't signed yet, so Windows may warn you the first time — the published checksum is the check that means something, and the installer does it for you — and moving a single huge file (a model, a container disk) needs Developer Mode switched on. Moving a folder doesn't, and a folder is nearly everything. With it off, stowit refuses rather than leaving a copy behind and telling you it freed space it didn't.
This page does not read your disk. Browsers could ask for folder
access, but we won't put that dialog on a customer. Your real number comes from the installed
app — stowit proof — which reads locally and prints three honest figures before
you move a byte.
The menu-bar glance — in design. Today this same status is one bare
stowit in your terminal; the app that renders it is next.