Wails: Go Desktop Applications with Web UI
/wails
Wails is a Go framework that packages a native web-rendered UI and a Go backend into one compiled binary, with no bundled browser engine. Reach for it if you write Go and want a lightweight desktop shell around your app instead of learning Rust or carrying Electron's footprint. Skip it if your team lives entirely in JavaScript and would rather avoid touching Go.
Building Desktop Apps with Go and Web Technologies
Wails is a framework for building desktop applications in Go, wrapping a Go backend and an HTML/JS/CSS frontend into a single binary. It renders that frontend through the operating system's native rendering engine rather than a bundled browser, and its CLI scaffolds new projects and auto-generates TypeScript definitions from your Go structs and methods.
Key Capabilities of Wails
- ✓Go handles the backend logic; the frontend can be React, Vue, Svelte, or Angular — all four show up among the repo's own GitHub topics.
- ✓Go methods are callable directly from JavaScript, and Wails auto-generates TypeScript definitions from your Go structs and methods so those calls are typed.
- ✓A shared eventing system lets Go and JavaScript emit and listen for the same events without hand-rolled message passing.
- ✓Native dialogs and menus, plus dark/light mode, come from the OS rather than being rebuilt in HTML and CSS.
- ✓Translucency and 'frosted window' effects are supported on platforms where the OS offers them.
- ✓The CLI scaffolds new projects from templates and handles compiling and bundling into a single binary.
- ✓No embedded browser. Wails renders through each OS's native rendering engine instead of shipping a Chromium copy.
Getting Started with Wails Installation
Wails ships two actively maintained versions with their own install command. v2, the stable line, installs via `go install github.com/wailsapp/wails/v2/cmd/wails@latest`, with full setup instructions at wails.io. v3, currently in beta, installs via `go install github.com/wailsapp/wails/v3/cmd/wails3@latest`, documented separately at v3.wails.io. Platform-specific system dependencies aren't detailed in the README excerpt — check whichever docs site matches the version you're installing.
Developing Applications with Wails (v2 and v3)
Usage isn't spelled out step-by-step in the README beyond the two install commands — it points to the full docs sites (wails.io for v2, v3.wails.io for v3) rather than walking through commands in the repo itself. What the README does establish: the CLI handles project generation, compiling, and bundling; Go methods get called directly from JavaScript; and new functionality goes through a formal WEP (Wails Enhancement Proposal) process — submitted as a draft pull request rather than a feature-request issue — with the project roadmap tracked in a GitHub Discussions thread.
Strengths
- ✓One compiled binary output — no separate runtime or embedded browser download bundled alongside your app.
- ✓TypeScript bindings are generated from your actual Go structs and methods, so the frontend gets typed calls instead of hand-rolled API wrappers.
- ✓MIT license, so there's no copyleft obligation or licensing friction for commercial use.
- ✓Bring-your-own frontend — React, Vue, Svelte, and Angular are all listed among the repo's own topics, so templates aren't locked to one JS framework.
- ✓Native dialogs, menus, and dark/light mode come from the OS rather than being reimplemented in HTML.
Understanding Wails' Scope and Target Audience
- △v3 is beta — the README lists it as Beta status, so production usage still means riding on the more mature v2 line.
- △No embedded browser is a strength until it's a limitation: rendering depends on each OS's own native engine, which means frontend behavior can differ slightly across Windows, macOS, and Linux instead of one consistent Chromium runtime everywhere.
- △The README excerpt doesn't document platform-specific setup dependencies, error troubleshooting, or a step-by-step build tutorial — you're routed to external docs sites for that.
- △It only helps if your backend logic is (or can be) Go — teams standardized on Node, Python, or JVM backends get no benefit from adopting it.
Wails Compared to Other Desktop Frameworks
Common Questions About Wails
Wails can replace Electron for many use cases — it's built for Go developers who want a lightweight desktop app or a frontend bolted onto an existing Go program, and it includes native menus and dialogs. It's a narrower tool than Electron, built specifically around a Go backend rather than Node.
Wails targets Go programmers who want to package an HTML/JS/CSS frontend with their application instead of running a local server and opening it in a browser tab.
Wails v2 is the stable, production-ready line, installed via `go install github.com/wailsapp/wails/v2/cmd/wails@latest`. Wails v3 is in beta, installed via `go install github.com/wailsapp/wails/v3/cmd/wails3@latest`, with its own separate documentation site.
Wails is released under the MIT license, based on the repository's license metadata.
Wails works with whatever frontend technology you already know — the repository's own topics list React, Vue, Svelte, and Angular, and the CLI ships templates to scaffold a project in any of them.
Wails does not embed a browser engine — it renders the frontend using each operating system's own native rendering engine instead of bundling something like Chromium, part of why its compiled binaries stay smaller than typical Electron apps.
The problem it solves
Go programs that want a GUI usually mean running a local web server and opening a browser tab, or reaching for a heavyweight browser-bundling framework just to get a window. Wails skips both. It compiles the Go backend and an HTML/JS/CSS frontend into one binary and renders it through the OS's own engine, so there's no server process to babysit and no Chromium copy riding along.
Best use cases
- •Turning an existing Go CLI or service into a desktop app with a GUI, without spinning up a local web server and browser tab.
- •Building cross-platform utilities (Windows, macOS, Linux) where the team already knows Go and a JS framework like Vue or Svelte.
- •Shipping a single-binary desktop tool for internal or developer-facing use, where installer size and dependency count matter.
- •Prototyping a desktop UI quickly using the CLI's generated templates for React, Vue, Svelte, or Angular.
Who should try it — and who should skip
Try Wails if you're a Go developer who wants a desktop front end for a CLI, internal tool, or service, and you're comfortable writing (or generating) an HTML/JS/CSS UI with React, Vue, Svelte, or Angular. Skip it if your app's backend isn't Go and switching languages isn't on the table, or if you need pixel-identical rendering across every OS rather than each platform's native engine.
Related repositories
Curious whether wails is right for you?
Let ChatGPT, Claude, or Perplexity look into it — click below and see what AI actually says about wails.