Video summary

Windows 11 vs Tiny 11: Does Debloating Offer Better Performance?

Main summary

Key takeaways

Technology

Summary of the Video Subtitles (Tech + Product Evaluation)

Context / Safety Note

  • The creator previously demonstrated how to build a custom “debloated” Windows 11 ISO using Tiny11 Builder and Microsoft’s official Windows 11 image.
  • They caution that pre-debloated ISOs from unknown sources can be risky, since malicious actors could reuse those builds.
    • Emphasis: use reputable sources and/or build from the official image.

What Tiny11 is Tested For

The main question of the video: Does debloating Windows 11 into Tiny11 improve performance?

The creator evaluates:

  1. Resource usage (RAM + disk space)
  2. Gaming performance across multiple titles

Benchmarks / Measurements

1) System Resource Usage

Compared to a “factory” Windows 11 install (with the latest Windows updates applied):

  • RAM usage: Tiny11 uses ~700 MB less memory than default Windows 11.
  • Cached memory:
    • Windows 11: ~4.8 GB cached
    • Tiny11: ~4.1 GB cached (consistent with the ~700 MB reduction)
  • Disk usage:
    • Windows 11: ~41 GB
    • Tiny11: ~33.9 GB
    • Savings: a little over ~7 GB

Framing: The creator says the goal here isn’t mainly to save storage—it’s to reduce resource usage that might improve gaming performance.

2) Gaming Performance Test Results (Mostly Within Margin of Error)

They test at 3440×1440 ultrawide across multiple games, comparing Windows 11 vs Tiny11.

Overall result: no meaningful FPS improvement for Tiny11; differences are largely within benchmark margin of error.

Game-by-game results (Windows 11 → Tiny11)

  • Black Mesa (Ultra): 175.1 avg / 112.2 1% low → 174.4 avg / 113.9 1% low

    • Tiny11 loses by ~0.7 FPS avg (negligible)

  • GTA V (High):

    • Note: Tiny11 triggered a Microsoft Store overlay prompt on first launch; the game otherwise works. 125.2 avg / 89.8 1% low → 125.4 avg / 89.6 1% low

    • Tiny11 wins by ~0.2 FPS (tiny, not noticeable)

  • Shadow of the Tomb Raider (High + RTX + DLSS): 98.3 avg / 88.3 1% low → 98.1 avg / 88.3 1% low

    • Tiny11 loses by ~0.2 FPS

  • Red Dead Redemption 2 (Medium): 67.6 avg / 51.6 1% low → 67.4 avg / 52.7 1% low

    • Tiny11 loses by ~0.2 FPS (1% low slightly higher)

  • Cyberpunk 2077 (Medium + RTX/DLSS medium): 35.9 avg / 31.5 1% low → 34.8 avg / 29.5 1% low

    • Largest loss: over ~1 FPS avg and worse lows

Conclusion / Recommendation

  • The creator did not observe meaningful real-world performance gains from Tiny11.
  • Default Windows 11 performed the same or slightly better in most cases.
  • Tiny11’s only apparent “wins”:
    • Slight improvement in frame timings, suggested by better 1% low / 0.1% low metrics
    • However, it was described as unnoticeable in gameplay
  • Hypothesis: the system may be GPU-bound (CPU usage stayed mostly below 50%, often around the 30s), so debloating may not help much on GPU-limited setups.
  • They consider repeating the tests on a lower-spec system to see if results change, but don’t plan to unless viewers want it.

Compatibility / Usability Drawbacks Noted

  • Tiny11 can cause compatibility issues.
  • Example:
    • Tiny11 does not include Microsoft Edge
    • Some software expects Edge to exist and could break
  • Observed issue:
    • GTA V launch overlay error requesting the Microsoft Store—seen once, then resolved on later launches.
  • Because of these issues, they state they:
    • don’t debloat on customer machines
    • don’t use deep-loaded copies personally

Stated Test System

  • CPU: Ryzen 5 5600H (subtitles show “hundred,” but context indicates Ryzen 5 5600)
  • RAM: 32 GB
  • GPU: RTX 3060 (CPU and GPU water-cooled)
  • Both OS installs were tested after applying Windows updates.

Main Speakers / Sources (at End)

  • Main speaker/source: The video’s creator/tester (no name provided in subtitles)
  • Primary external source mentioned: Microsoft Windows 11 official image (used for building Tiny11 via Tiny11 Builder)

Original video