Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/flick9000/winscript/llms.txt

Use this file to discover all available pages before exploring further.

Winscript gives you two complementary ways to control which tweaks are applied: an interactive GUI for hands-on customization, and a JSON configuration file system for saving, sharing, and automating your selections. This page covers every configuration option — from the Export/Import buttons in the UI to the built-in presets and the command-line import flag for scripted or unattended deployments.
All Winscript operations — including importing a config and running the generated script — require an administrator PowerShell or terminal session. Ensure you launch Winscript with elevated privileges before applying any tweaks.

Import & Export

Winscript’s config system lets you snapshot your current selections and replay them anywhere, making it straightforward to maintain a consistent setup across multiple machines or Windows reinstalls.

Exporting a Configuration

After selecting your tweaks in the GUI, click the Export button in the toolbar. Winscript saves all current toggle states to a single JSON file at the path you choose. The file is human-readable and version-control friendly, so you can store it alongside your dotfiles or in a team repository.

Importing a Configuration

To restore a previously saved configuration, click the Import button and select your JSON file. All toggles will be set to match the saved state, ready for you to review before running or downloading the script.

Automating with the CLI Flag

For unattended or automated workflows, use the -i flag when launching the executable. Winscript reads the specified config file on startup and pre-loads all selections without any manual interaction:
.\winscript.exe -i "C:\path\to\config.json"
This is the recommended approach for:
  • IT administrators deploying consistent configurations across a fleet of machines
  • Post-install automation — pair with the Unattended Setup feature to apply your tweaks immediately after a fresh Windows installation
  • Repeatable dev/lab setups where you want the same optimizations every time you rebuild
The -i flag corresponds to the --import CLI argument defined in the app’s Tauri configuration and accepts any valid absolute or relative path to a Winscript JSON config file.

Presets

Not sure where to start? Winscript ships with three built-in presets that cover the most common use cases. Each preset is a curated selection of tweaks balanced for a different risk/reward profile.
PresetDescription
BasicRecommended for most users. Strikes a good balance between privacy, performance, and functionality — safe to apply on everyday machines.
StrictHeavy focus on privacy and performance. Disables some non-essential features that average users may not notice but power users can live without.
ExtremeNot recommended for general use. Applies the most aggressive tweaks and breaks some Windows features — only use this if you know exactly what you’re doing.
Select a preset from the Winscript interface to instantly load its associated toggle states, then fine-tune individual options before generating your script. See Scripts → Apps → Presets for the full line-by-line breakdown of what each preset enables and disables.

Script Output

When your configuration is ready, Winscript offers two ways to deliver the generated PowerShell script:

Run Script

Executes the generated .ps1 script immediately against the current system. Changes take effect right away — some tweaks (such as disabling certain services or removing components) may require a system reboot to fully apply. Use this option when you’re working directly on the target machine and want instant results.

Download Script

Saves the generated .ps1 file to a location of your choice without running it. This lets you:
  • Inspect the script before applying any changes
  • Schedule execution via Task Scheduler or a deployment tool
  • Deploy to other machines by copying the file and running it with administrator privileges
  • Keep an audit trail of exactly what was applied and when
To run a downloaded script manually, open an administrator PowerShell window and execute:
Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass
.\your-winscript-output.ps1

Language Support

Winscript’s GUI is fully localized into 13 languages, so you can work in your native language without switching your Windows display language:
LanguageLocale code
Englishen
Germande
Spanishes
Frenchfr
Hungarianhu
Italianit
Koreanko
Portuguesept
Russianru
Swedishsv
Turkishtr
Vietnamesevi
Simplified Chinesezh-CN
The UI language is detected automatically from your Windows locale settings. All 13 translations cover the full interface including tweak descriptions, preset names, and button labels.

Build docs developers (and LLMs) love