If you want to explore Microsoft’s Windows UI controls without creating a project first, install WinUI 3 Gallery from the Microsoft Store. If you need to inspect or change the sample implementation, clone Microsoft’s WinUI Gallery repository and build it in Visual Studio. The phrase “WinUI Gallery 3.0” is commonly used in searches, but Microsoft’s official materials identify the app as WinUI 3 Gallery or WinUI Gallery; they do not verify a separately numbered Gallery release called “3.0.”
The Store route is the quickest way to interact with controls and read the accompanying XAML and code examples. The source route requires developer tooling and is intended for examining, modifying, or debugging the project. The instructions below cover both paths, explain the requirements that apply to each, and show how to run the samples safely when the repository uses experimental Windows App SDK features.
As an Amazon Associate I earn from qualifying purchases.
What WinUI 3 Gallery is
WinUI 3 Gallery is an interactive Windows application for learning the controls, styles, features, and design guidance available to Windows App SDK desktop applications. Microsoft’s project README describes it this way: “This app demonstrates all of the WinUI 3 controls and styles available to make a modern Windows app with the Windows App SDK.”
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteEach control page combines a working example with the markup and code-behind used to create it. That makes the Gallery useful for more than visual browsing: you can see a control’s behavior, inspect its XAML, and then adapt the pattern in your own project. The app also covers adaptive user interfaces, design guidance, and accessibility considerations.
#1 Best Overall
WinUI is Microsoft’s native Windows UI framework and is delivered as part of the Windows App SDK. Microsoft documents WinUI framework support for Windows 10 version 1809 (build 17763) and later, including Windows 11. That framework compatibility statement should not be treated as the current Microsoft Store listing’s separate operating-system requirement; check the listing shown on your PC for the app’s current availability.
The name matters when you search. Microsoft documentation generally says WinUI 3 Gallery, while the source repository is named WinUI Gallery. “3.0” is useful search wording because it signals the WinUI 3 generation, but it is not a confirmed Gallery release number. Use Microsoft’s Samples and tools page or the repository link rather than relying on third-party download pages that may use a different name.
Choose the installation route that fits your goal
| Route | Setup effort | Best for | What you can do |
|---|---|---|---|
| Microsoft Store | Install and launch the published app | Exploring controls, styles, guidance, and code examples | Use the released Gallery experience without configuring a development environment |
| GitHub source and Visual Studio | Install developer tools, clone the repository, then build | Inspecting implementation details or changing the samples | Read, modify, rebuild, and debug the Gallery project |
You do not need Visual Studio merely to install the Store app. Conversely, a source checkout is not required for casual exploration. Use the Store path first if you only want to understand what a control does; use the repository when you need the exact project files or want to experiment with changes.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
The two copies may not be identical at a given moment. The Store package is the published application Microsoft distributes, while a checkout reflects the commit and dependency versions you cloned. A source build can therefore expose a newer, older, or experimental example than the package currently shown in Microsoft Store.
Install WinUI 3 Gallery from Microsoft Store
1. Open Microsoft’s official Gallery listing
Go to Microsoft’s official Samples and tools page and open its WinUI 3 Gallery link. That link directs you to the Microsoft Store listing. The Store destination and its listing details can change, so confirm the current availability, region, and displayed app version in the Store itself rather than relying on an old screenshot or a search result.
This is also the safest way to distinguish the Gallery from unrelated WinUI sample projects. The official page presents both the ready-to-use Store app and the public source repository, so you can switch routes without hunting for unofficial mirrors.
2. Install and launch
- On the Store page, choose the installation command offered by Microsoft Store.
- Wait for the installation to finish, then select Open. You can also launch the Gallery later from the Start menu.
- If the listing is unavailable, check that Microsoft Store is signed in and that your Windows region permits the listing. The source-build route remains available through Microsoft’s public repository.
No Visual Studio project, SDK selection, or source checkout is needed for this route. The Store package supplies the application as distributed by Microsoft. If Store reports that the app cannot be installed, record the exact message and first verify listing availability and region; do not install a similarly named package from an unverified site.
3. Find and use the samples
Browse the navigation categories for controls and features. Open a sample page, interact with the control in the live preview, and then read the displayed XAML and code-behind. Change focus, keyboard state, window size, or other available options while testing; these interactions often reveal behavior that is not obvious from a static screenshot.
- Controls and styles: compare common WinUI controls and their visual states.
- Code and markup: use the example’s XAML and code-behind as a starting point for your own implementation.
- Adaptive UI: observe how layouts respond to available window space.
- Design guidance: review recommendations that explain how a control should be used, not just how it is instantiated.
- Accessibility: use the accessibility material to check interaction and presentation requirements while you learn a control.
Read the markup alongside the live preview instead of copying only a property value. The surrounding layout, styles, event handlers, and accessibility guidance often explain why the sample behaves as it does. Treat the example as a focused reference: isolate the control or pattern you need, then verify it in the context of your own app.
The Gallery is a learning and reference application. A sample’s appearance or API usage is not automatically a promise that every API shown is stable in every Windows App SDK release, particularly in the source build described below.
Build the Gallery from Microsoft’s source
Requirements for the repository build
The repository’s quick-start instructions require:
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Rank #2
- Visual Studio 2022 or later.
- Windows 10 or later to execute the application.
- The Visual Studio Windows application development component.
These are project-specific repository instructions. They are different from the requirements for creating a brand-new WinUI application using Microsoft’s current quickstart, and they are not prerequisites for the Microsoft Store installation.
Visual Studio must be able to restore the solution’s packages and compile Windows application projects. If the required component is missing, add it through the Visual Studio Installer before treating package or compiler errors as a source-code problem. Keep the repository’s documented versions in mind: its README says “Visual Studio 2022 or later,” even though Microsoft’s separate new-app quickstart now describes Visual Studio 2026.
1. Clone the repository
Open a terminal in the folder where you keep development projects and run:
git clone https://github.com/microsoft/WinUI-Gallery.gitAfter the command completes, change into the new repository directory in your preferred way. If Git is not installed, install a Git client before attempting the clone; the repository itself is hosted publicly by Microsoft.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Cloning gives you the project files, sample assets, solution metadata, and configuration used by the Gallery. Keep the checkout in a writable location so Visual Studio can create intermediate build and package-restore files. If you plan to compare your edits with the original, make a copy or use a separate branch rather than modifying the only checkout you have.
2. Open the solution
Start Visual Studio and open WinUIGallery.slnx from the cloned directory. Allow Visual Studio to restore the solution’s packages when prompted. The repository’s current solution format is the .slnx file, so open that file rather than guessing an older solution name.
Package restore can take a while on the first open. Let it complete before deciding that a project is missing. If Solution Explorer shows unloaded projects, use the exact error text to determine whether the issue is a missing Visual Studio component, package restore, or an unsupported configuration.
3. Build with the Gallery project selected
- In Solution Explorer, confirm that the
WinUIGalleryproject is present. - Set
WinUIGalleryas the startup project. The repository README specifically calls for this selection. - Select the normal Debug or Release configuration.
- Build the solution. Let package restore finish before diagnosing compilation errors.
Choosing the startup project is important when the solution contains supporting projects. If another project remains selected, Visual Studio can build successfully but launch the wrong target or offer no useful runnable target. Debug is convenient while you inspect code; Release is useful when you want to see the normal optimized configuration. The README does not require a special Gallery-only configuration.
Recommended Free Tools
4. Run the samples
Start the selected project from Visual Studio using the usual run command or F5. The Gallery window should open as a locally built Windows application. Use the same navigation and live examples as in the Store version, while remembering that the source build reflects the checkout and package versions you built, not necessarily the Store package currently offered to users.
To study an implementation, open the relevant sample files while the app is running, make a small change, rebuild, and run again. This loop lets you connect a XAML property or code-behind handler to the visible result. Keep changes incremental: a minimal edit makes it easier to tell whether a behavior comes from your change, the sample, or the SDK version pinned by the repository.
Understand the repository’s experimental Windows App SDK
The Gallery repository uses an experimental Windows App SDK to demonstrate upcoming features. Its SDK version is pinned in standalone.props, and the application bundles the runtime instead of referencing a shared Windows App SDK framework package. Those choices make the checkout more self-contained, but they also mean that the project is intentionally showing APIs that may not yet be stable.
Bundling the runtime means the source build uses the version selected by the project rather than silently taking a different shared framework installed on the machine. The pinned value in standalone.props is therefore an important diagnostic detail: note it when you report a build result or compare behavior with another checkout.
Experimental APIs can change or be removed before a stable release. The repository’s Windowing APIs page mixes stable and experimental examples; experimental examples are individually labeled and carry warnings. If an example fails after you update the repository, first check whether the API is marked experimental and whether the checkout’s pinned SDK has changed.
Do not treat a successful Gallery build as proof that an experimental API is suitable for production without reviewing the corresponding Windows App SDK documentation and release status. The sample’s purpose is to demonstrate the API, including features that are still evolving. A warning on an individual page is a signal to verify contracts, availability, and migration guidance before copying the pattern into a shipped product.
Fix the documented NuGet-assets build failure
The repository documents a specific failure in which the build reports missing NuGet assets. For that repository issue, its suggested workaround is:
- Close the active build or stop Visual Studio.
- Delete the repository’s
nuget.configfile. - Reopen the solution and build again.
This is a workaround for the Gallery repository’s documented broken-build condition, not a universal repair for every NuGet or Visual Studio problem. If the error is different, preserve the exact message and check package-restore output before changing configuration files. Removing a NuGet configuration can affect package sources, so do not apply this step indiscriminately to unrelated projects.
Free tools Windows power users keep installed
One-click scans. No signup required.
After deleting the file, restore and build only the Gallery checkout you are troubleshooting. If the workaround resolves the missing-assets message, keep a note of the change so another developer understands why the local setup differs from a fresh clone. If it does not, restore the configuration from version control and investigate the actual package or workload error instead of repeatedly deleting files.
Store installation versus source build: a practical decision
Use this quick decision process:
- You only want to browse and run examples: install from Microsoft Store.
- You want to read the implementation: clone the repository and open the solution in Visual Studio.
- You want to change a sample: use the source build so your edits can be compiled and tested.
- You are evaluating an upcoming API: use the repository, read the experimental labels, and expect API changes.
The Store route minimizes setup and gives you the published interactive experience. The source route trades that convenience for control over the files, build configuration, and code you inspect.
There is no requirement to choose one route permanently. Many readers start with the Store app to identify a useful control, then clone the repository when the displayed snippet is not enough to understand layout, event handling, or a related sample. Conversely, a developer who has built the repository can still install the Store package to compare the published experience with a local checkout.
Do not confuse Gallery setup with creating a new WinUI app
Microsoft also publishes a current “Build your first WinUI app” quickstart. That is a separate path for starting your own application, not a prerequisite checklist for installing Gallery.
Visual Studio path for a new app
The current quickstart specifies Visual Studio 2026, the WinUI application development workload, Developer Mode, and the WinUI Blank App (Packaged) C# template. After creating the project, press F5 to run it. Those requirements apply to a new application created through that quickstart; the Gallery repository itself documents Visual Studio 2022 or later.
The distinction prevents a common setup mistake. Installing Developer Mode, selecting a packaged template, or upgrading Visual Studio may be appropriate for a new project, but none of those steps is presented as a condition for opening the Store Gallery. Follow the instructions for the task you actually intend to perform.
Terminal path for a new app
Microsoft’s documented command-line path specifies .NET SDK 10 or later, winapp CLI 0.6 or later, and Developer Mode. The commands shown by the quickstart are:
winapp new --name MyWinUIApp --template winui --use-defaults
cd MyWinUIApp
winapp runUse this path only when your goal is to create a separate WinUI application. It does not replace the Gallery repository’s Visual Studio build instructions. The CLI’s .NET and winapp versions should not be retroactively treated as dependencies of the Gallery checkout unless that repository’s own documentation adds them.
Requirements and version boundaries at a glance
| Task | Documented requirements | Important qualification |
|---|---|---|
| Install the Gallery package | Microsoft Store access | Check the listing for current region, availability, and app details |
| Build Gallery from source | Visual Studio 2022 or later; Windows 10 or later to execute; Windows application development component | These come from the Gallery repository README |
| WinUI framework support | Windows 10 version 1809 (build 17763) and later, including Windows 11 | This is framework compatibility, not a Store listing promise |
| Create a new app with the Visual Studio quickstart | Visual Studio 2026; WinUI application development workload; Developer Mode; WinUI Blank App (Packaged) C# template | Applies to a new project, not the Store Gallery install |
| Create a new app with the CLI quickstart | .NET SDK 10 or later; winapp CLI 0.6 or later; Developer Mode | Uses the documented winapp new and winapp run commands |
Keep the boundaries in this table when planning a setup. “Windows 10 or later to execute” is the repository’s source-build guidance, while “Windows 10 version 1809 (build 17763) and later” is Microsoft’s framework support statement. Neither line supplies a current Store listing promise, which is why the Store page remains the authority for that package’s availability.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Common mistakes to avoid
- Searching for a verified “3.0” release number: the official name is WinUI 3 Gallery or WinUI Gallery; “3.0” describes the WinUI generation in the reader’s query, not a confirmed Gallery app version.
- Installing Visual Studio for Store exploration: the Store package is the simplest path and does not require a source build.
- Opening the wrong solution file: use
WinUIGallery.slnxfrom the repository. - Leaving another project as startup: select
WinUIGallerybefore pressing F5. - Assuming every sample is stable: inspect labels on the Windowing APIs page and account for the experimental SDK.
- Applying the NuGet workaround everywhere: deleting
nuget.configis the repository’s specific suggestion for its documented missing-assets failure, not a general package-management rule. - Using new-app requirements as Gallery requirements: the Visual Studio 2026, .NET 10,
winapp, and Developer Mode details belong to Microsoft’s separate app-creation quickstart. - Assuming the Store and checkout are synchronized: a published package and a cloned commit can contain different examples or dependency versions.
- Copying an experimental API without checking its label: the Windowing APIs page identifies experimental examples individually and warns that they may change or disappear.
A reliable first session
- Install the Store Gallery if your immediate goal is to understand controls visually.
- Open a control page, interact with it at several window sizes, and read both its markup and code-behind.
- Note any adaptive-layout or accessibility guidance associated with the example.
- Clone the repository when you need to trace behavior, compare implementation choices, or edit a sample.
- Build the checkout in Visual Studio with
WinUIGalleryas the startup project and Debug or Release selected. - Before relying on a newer example in your own software, verify whether it is marked experimental and check the Windows App SDK version used by your project.
For a repeatable comparison, record whether you used the Store package or a source checkout, the Windows version, and the repository commit or pinned SDK value. That simple context helps explain why a control may look or behave differently between two machines without assuming that either installation is defective.
Frequently asked questions
Is WinUI Gallery 3.0 the official name?
No. Microsoft’s documentation uses WinUI 3 Gallery, and the GitHub project is called WinUI Gallery. “3.0” is not verified as a separate Gallery release number.
Can I use the Gallery without Visual Studio?
Yes. Install the published app through Microsoft Store to browse and run the samples. Visual Studio is required for the repository build described by Microsoft’s README, not for Store exploration.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Where do I get the source?
Use Microsoft’s public repository at https://github.com/microsoft/WinUI-Gallery, clone it with Git, and open WinUIGallery.slnx in Visual Studio.
Which project should I run?
Select WinUIGallery as the startup project, choose the normal Debug or Release configuration, and run it from Visual Studio.
What Windows version does WinUI support?
Microsoft documents WinUI framework support beginning with Windows 10 version 1809 (build 17763), including Windows 11. The Store listing can have separate current requirements, so check it directly.
Why does a source build use an experimental SDK?
The Gallery demonstrates upcoming Windows App SDK features. The repository pins its SDK in standalone.props and bundles the runtime. Experimental APIs can change or be removed before they become stable.
What should I do about missing NuGet assets?
For the specific broken-build condition documented by the repository, stop Visual Studio, delete the repository’s nuget.config, reopen the solution, and build again. Do not use that workaround as a general fix for unrelated NuGet errors.
Do I need .NET 10, the winapp CLI, or Developer Mode?
Those are requirements in Microsoft’s separate quickstart for creating a new WinUI app through the terminal. They are not listed as prerequisites for installing the Store Gallery or building the Gallery repository, whose README specifies Visual Studio 2022 or later and the Windows application development component.
Frequently Asked Questions
Is WinUI Gallery 3.0 the official name?
No. Microsoft’s documentation uses WinUI 3 Gallery, and the GitHub project is called WinUI Gallery. “3.0” is not verified as a separate Gallery release number.
Can I use the Gallery without Visual Studio?
Yes. Install the published app through Microsoft Store to browse and run the samples. Visual Studio is required for the repository build, not for Store exploration.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Where do I get the source?
Clone Microsoft’s public repository at https://github.com/microsoft/WinUI-Gallery and open WinUIGallery.slnx in Visual Studio.
Which project should I run?
Select WinUIGallery as the startup project, choose Debug or Release, and run it from Visual Studio.
What Windows version does WinUI support?
Microsoft documents WinUI framework support beginning with Windows 10 version 1809 (build 17763), including Windows 11. Check the Store listing for the package’s current requirements.
Why does a source build use an experimental SDK?
The Gallery demonstrates upcoming Windows App SDK features. Its SDK is pinned in standalone.props and the runtime is bundled, so experimental APIs can change or be removed.
Free tools Windows power users keep installed
One-click scans. No signup required.
What should I do about missing NuGet assets?
For the repository’s documented failure, stop Visual Studio, delete its nuget.config, reopen the solution, and build again. This is not a universal NuGet fix.
Do I need .NET 10, winapp CLI, or Developer Mode?
Those requirements belong to Microsoft’s separate quickstart for creating a new WinUI app, not to the Store Gallery installation or the repository build instructions.
The Bottom Line
Install WinUI 3 Gallery from Microsoft Store for the fastest way to explore controls, styles, adaptive UI, design guidance, accessibility material, and working code examples. Clone Microsoft’s WinUI Gallery repository when you need to inspect or modify the implementation: open WinUIGallery.slnx in Visual Studio 2022 or later, select WinUIGallery as the startup project, and run Debug or Release. Remember that the source checkout uses a pinned, experimental Windows App SDK, so verify labels and API stability before carrying a sample into production.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Recommended Free Tools
