Remote website
Point the project at a web URL. InstallerLab writes the WebView2 host configuration and prepares the Windows application.
Turn a URL or local HTML app into a Windows desktop application — then deploy it from the same project.
Web-to-EXE is a first-class InstallerLab project type. Define a remote URL or a local web application, configure the Windows WebView2 host, and use the same editable FSS project to create a single-file Web-to-EXE application, Setup EXE, MSI or WiX Burn Bundle.
URL → EXELocal HTML → EXEWebView2Setup EXEMSIBundleFSS
One project, two jobs: create the desktop app and create its installer.
Local HTML application
Use a local application folder containing index.html. The local web payload becomes part of the generated Windows application.
Single-file Web-to-EXE
The prepared WebView2 application can be wrapped into a single-file output through InstallerLab's portable engine.
Installer targets
The same WebToExe project can generate Setup EXE, MSI or Bundle without first exporting to another authoring tool.
Self-contained runtime
WebView2 is packaged with the generated application. The end user does not need to install WebView2 separately.
Project-aware output
InstallerLab disables classic Portable and B4J Portable targets for WebToExe projects and exposes only the targets that match this project type.
Control how the web application behaves inside Windows.
| Setting | Purpose |
|---|---|
| Web URL | Remote application or site loaded by the WebView2 host. |
| Local web app folder | Optional local HTML application whose entry point is index.html. |
| Theme | Follow system, Light or Dark. |
| Navigation toolbar | Show or hide the host navigation UI. |
| External links | Choose whether external navigation opens in the system browser. |
| Block PWA install | Prevent the hosted website from presenting its own PWA installation path inside the desktop host. |
| Hide elements | Hide DOM elements by ID, CSS class or CSS selector. |
| Disable elements | Disable DOM elements by ID, CSS class or CSS selector. |
Build-target matrix for WebToExe.
| Target | WebToExe | Notes |
|---|---|---|
| Web-to-EXE single-file app | ✓ | Prepared WebView2 application wrapped as one executable. |
| Setup EXE | ✓ | Installer around the self-contained WebView2 application. |
| MSI | ✓ | Windows Installer package for the self-contained WebToExe application. |
| Bundle | ✓ | WiX Burn packaging for the same self-contained WebToExe application. |
| Classic Portable | — | Not the WebToExe target; classic Portable belongs to Application projects. |
| B4J Portable | — | Dedicated B4J workflow, not applicable to WebToExe projects. |
Online or fully local/offline.
Online URL mode
Point WebToExe at a live URL. The Windows app loads the current online application, so server-side updates appear without rebuilding the desktop package.
Local HTML mode
Package the HTML, CSS, JavaScript, images and other local assets with the Windows application. The UI can run without Internet access when the application itself does not depend on remote APIs or resources.
A project can therefore choose between a live online application and a self-contained local web application. Local mode removes the dependency on a website being reachable; only intentionally remote services remain network-dependent.
Community and PRO behavior.
Community
URL-to-single-file Web-to-EXE conversion is available without the advanced Web-to-EXE restrictions.
PRO
Local HTML applications, DOM element customization and WebToExe Setup EXE/MSI/Bundle installer targets require InstallerLab PRO.
Customize an existing web app without rewriting it.
The Windows host can alter what the user sees and can interact with, even when you do not control the original website source.
Hide by ID
Remove selected interface elements identified by their DOM ID.
Hide by class
Hide groups of elements using their CSS class.
Hide by selector
Target more precise interface areas with CSS selectors.
Disable instead of hide
Keep an element visible but prevent interaction, also by ID, class or CSS selector.
Price matters too.
Community
InstallerLab remains free for the Community feature set, including the basic URL-to-Web-to-EXE path.
PRO from US$10
An optional contribution of US$10 or more can request one-machine PRO activation after verification. PRO includes the advanced WebToExe features such as local HTML, DOM customization and installer targets.
Why this is different from a “Web Installer”.
A traditional web installer is an installer bootstrapper that downloads installation resources from the Internet. Web-to-EXE solves a different problem: it turns the web application itself into a Windows desktop application and then packages that application.
InstallerLab v4
URL / local HTML → WebView2 Windows app → EXE / Setup / MSI / Bundle inside the same project model.
Traditional installer workflow
An existing Windows application or installer is packaged or downloaded. The installer tool does not necessarily create the desktop application from the website.
See the comparison page for the official sources reviewed on October 7, 2026.
FSS remains the source of truth.
[Setup]
ProjectType=WebToExe
AppName=My Web App
AppVersion=1.0.0
OutputDir=C:\Builds
[WebApp]
Url=https://example.com
Theme=System
ShowToolbar=True
BlockPwaInstall=True
AllowExternalLinks=TrueThe exact stored keys are managed by InstallerLab. Advanced users can still inspect and version the FSS project like the rest of the InstallerLab workflow.
Web-to-EXE FAQ
Does InstallerLab just create a shortcut to a website?
No. The v4 workflow prepares a Windows WebView2 host and its configuration, then builds the requested Windows artifact.
Can I package local HTML instead of a public URL?
Yes. A local web application folder can be used for PRO WebToExe projects.
Can one project generate both the app and its installer?
Yes. That is the key v4 workflow: the WebToExe project defines the web application and also drives its supported deployment targets.
Does the target PC need WebView2 installed?
No. InstallerLab v4 packages WebView2 as self-contained runtime content with the generated application, so no separate WebView2 installation is required.
From web application to Windows deployment without changing project systems.
InstallerLab v4 combines web application wrapping and Windows installer generation in the same visual/FSS workspace.