What "portable" means for a Windows program
A portable build is one that runs directly from an executable without going through a Windows installer. There's no setup wizard writing entries into the registry, no service registered to start at boot, and no files copied into C:\Program Files. Instead, the program keeps its configuration file next to its own executable, so the whole thing — program plus settings — can live in a single folder.
That single-folder design is what makes it copyable. Put the folder on a USB drive, a network share, or in cloud storage, and the program runs the same way from wherever you put it, on any compatible Windows machine, without leaving the installer's usual traces behind on that machine afterward.
When a technician actually reaches for a portable build
- USB toolkit — a technician carries a folder of diagnostic and cleanup tools on a flash drive and runs them on whichever machine needs attention, without installing anything permanent on client hardware.
- Locked-down machines — some corporate or shared PCs block software installation through Group Policy but still allow running an already-approved executable. A portable build can be the only option that runs at all in that environment.
- Incident response — when investigating a machine that might be compromised or that you don't want to modify more than necessary, running a tool without installing it keeps your footprint on that system smaller and easier to explain later.
Outside these cases, most home users are better off with a normal installed copy — see how to use TreeSize for the standard setup path — since an installed copy gets easier updates and closer integration with Windows.
The trade-offs of going portable
| Capability | Installed copy | Portable build |
|---|---|---|
| File Explorer right-click integration | Typically available | Usually not registered, since that requires writing to the registry |
| Automatic update checks | Common | Usually manual — you replace the folder yourself |
| Runs without admin rights | Often needs elevation for setup | Launches without an installer step, but still needs elevation to read protected folders |
| Leaves traces on the host machine | Yes, by design | Minimal, which is the whole point |
That last row on admin rights is worth underlining: a portable build sidesteps the installer, but it does not sidestep Windows permissions. Scanning C:\Users\<other account> or parts of C:\Windows still requires an elevated session regardless of whether the program was installed or run portably. See running as administrator for the elevation steps themselves.
Confirm availability with the developer, not assumptions
Not every edition of every Windows utility ships a portable build, and product lineups change over time. Rather than assuming a portable version exists for a specific TreeSize edition — or that its feature set matches the installed version exactly — check the developer's own download page for the current, authoritative answer. Our download guide points to where to start looking, and our safety overview covers how to verify you're getting a build from a legitimate source in general.
Portable builds: common questions
Does a portable build still need to be scanned for malware before use?
Yes. Portable executables are ordinary programs; running them without an installer doesn't change how antivirus scanning or source verification should work. Download only from a source you trust.
Can I run a portable build directly from a network share?
Will a portable build remember my settings between sessions?
Is a portable build less capable than the installed version?
Continue reading
Last reviewed by the jam-software.org editorial team on . Spotted something out of date? Tell us.