Nano11 compresses Windows 11 install footprint to as little as 2.8GB — 'extreme experimental script' is 3.5 times smaller than Tiny11 and comes with 'none of the fluff'
The PowerShell script should work with any version of Windows 11.
NTDEV has introduced the Nano11 Builder for Windows 11. This is a tool that allows Windows 11 testers and tinkerers to pare down Microsoft’s latest OS into the bare minimum. With this new release, the developer has significantly pushed the boundaries of their prior Tiny11 releases.
Nano11’s extreme pruning of the official installer disk image from Microsoft produces a new ISO “up to 3.5 times smaller” than the original. The example Windows 11 standard ISO shown in the Nano11 demo was 7.04GB, but after the PowerShell script had done its stuff, you can end up with a 2.29GB ISO.
Furthermore, the completed Windows 11 install can scrape in as low as 2.8GB if you use Windows 11 LTSC as the source ISO.
Before we talk anymore about Nano11, please be warned that it is described as “an extreme experimental script designed for creating a quick and dirty development testbed.” It could also be useful for Windows 11 VM (virtual machine) tests, suggests its developer. But it isn’t designed for installing a compact Windows 11 for your daily workhorse.
In the video above, NTDEV explains the process of creating a Nano11-pruned Windows 11 ISO. Then it demonstrates it installed on a virtual machine using the VMware Workstation app. In this app, the intrepid developer sets aside a meager 20GB virtual disk for the installation; other settings seem to be left at their defaults. The installation moves pretty quickly, but we think the video is also sped up a little to reduce viewer tedium.
At around 8m 34s into the video, there's a demo of the kind of Windows 11 you end up with after its Nano11 processing. In the words of the script developer, Nano11 Builder strips out “fluff like Windows Hello packages, unnecessary drivers, .NET precompiled assembly, IME components, wallpapers and more.” The Start Menu seems so bare…
Size is important
Some of the social media postings suggest that, when following in NTDEV’s Nano11 footsteps, you will end up with as little as a 2.8GB Windows 11 install footprint. However, this will depend on the 'flavor' of Windows 11 you start with, and there is also a little bit more work to be done to achieve the minimum size.
Get Tom's Hardware's best news and in-depth reviews, straight to your inbox.
After installation, the example Nano11 install actually uses up 11.0GB of the 20GB virtual disk in the VM. It is only after NTDEV runs the 'Compact' command on the C: drive using LZX compression and then deletes the virtual memory page file that we see the installation reduced to around the 3.2GB level.
The nano11 script used on a Win11 LTSC image leads to an even better result! This will be perfect for when you need an ISO that can be installed in like 5 minutes and without any (and I mean it) fluff https://t.co/iJXGKahIx4 pic.twitter.com/UVnsS6MlgGSeptember 9, 2025
When starting with the Windows 11 LTSC ISO as the source, NTDEV actually managed to end up with just a 2.8GB install, as shared in a post on X, and embedded above.
Follow Tom's Hardware on Google News, or add us as a preferred source, to get our up-to-date news, analysis, and reviews in your feeds. Make sure to click the Follow button!
Mark Tyson is a news editor at Tom's Hardware. He enjoys covering the full breadth of PC tech; from business and semiconductor design to products approaching the edge of reason.
-
93QSD5 If you are really this space-constraint, just avoid W11 altogether.Reply
I appreciate the tinkering but can't see the practicality, especially given that with W11 and general improvement in all sectors, the spec requirements have risen to the point where, you really shouldn't be running into space issues due to W11 install size.
Or just don't install W11. -
Dementoss Reply
It's made clear enough in the article, this is not for everyday use but, intended for test beds and VMs.93QSD5 said:If you are really this space-constraint, just avoid W11 altogether.
I appreciate the tinkering but can't see the practicality, especially given that with W11 and general improvement in all sectors, the spec requirements have risen to the point where, you really shouldn't be running into space issues due to W11 install size.
Or just don't install W11. -
EzzyB Reminds me of overclocking with liquid nitrogen. It's not actually practical, just something cool to try.Reply
I mean, lets give the VM 2GB of memory, then delete the page file! :p -
excalibur1814 This is what we're here for, p*ssi** around with computer stuff. It's there, it's been done, so if you wanted to give it a shot you can. Thankfully, we have these options.Reply -
Alvar "Miles" Udell I'd like to suggest to the Future PLC people who do hang around here that articles like this, that is articles about Tiny11 and other such projects relating to modification of Windows 11 and may be targeting a niche audience, be limited to Windows Central only.Reply -
USAFRet Reply
And we'll still get people here thinking that is a good option for a daily driver.Alvar Miles Udell said:I'd like to suggest to the Future PLC people who do hang around here that articles like this, that is articles about Tiny11 and other such projects relating to modification of Windows 11 and may be targeting a niche audience, be limited to Windows Central only. -
Alvar "Miles" Udell ReplyUSAFRet said:And we'll still get people here thinking that is a good option for a daily driver.
Sadly... -
Stomx Microsoft is Windows + Office for which MS squeezes your money. Few 1000 dollars probably for entire your life.Reply
But there exist similar or better OSes and similar other Office software. All free. There is no any compelling reason for MS even to exist. -
93QSD5 Reply
Even on a test bed or VM you wouldn't want to use a cutted iso image.Dementoss said:It's made clear enough in the article, this is not for everyday use but, intended for test beds and VMs.
I can't think of a single scenario where someone is doing lots of VM work and having to resort to this. Things don't add up. -
TerryLaze ReplyDementoss said:It's made clear enough in the article, this is not for everyday use but, intended for test beds and VMs.93QSD5 said:Even on a test bed or VM you wouldn't want to use a cutted iso image.
I can't think of a single scenario where someone is doing lots of VM work and having to resort to this. Things don't add up.
Yup, also you can use windows PE for that, should also be more usable than this is.
This is just general tomfoolery.