Need help with walk?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

5.7K Stars 786 Forks Other 1.7K Commits 316 Opened issues


A Windows GUI toolkit for the Go Programming Language

Services available


Need anything else?

Contributors list

About Walk

Walk is a "Windows Application Library Kit" for the Go Programming Language.

Its primarily useful for Desktop GUI development, but there is some more stuff.


Make sure you have a working Go installation. See Getting Started


Walk currently requires Go 1.11.x or later.

To Install

Now run

go get

Using Walk

The preferred way to create GUIs with Walk is to use its declarative sub package, as illustrated in this small example:

package main

import ( "" . "" "strings" )

func main() { var inTE, outTE *walk.TextEdit

    Title:   "SCREAMO",
    MinSize: Size{600, 400},
    Layout:  VBox{},
    Children: []Widget{
            Children: []Widget{
                TextEdit{AssignTo: &inTE},
                TextEdit{AssignTo: &outTE, ReadOnly: true},
            Text: "SCREAM",
            OnClicked: func() {


Create Manifest
            PerMonitorV2, PerMonitor

Then either compile the manifest using the rsrc tool, like this:

go get
rsrc -manifest test.manifest -o rsrc.syso

or rename the

file to
and distribute it with the application instead.
Build app

In the directory containing

go build

To get rid of the cmd window, instead run

go build -ldflags="-H windowsgui"
Run app
Sample Output (Windows 7)

alt tag

More Examples

There are some examples that should get you started.

Application Manifest Files

Walk requires Common Controls 6. This means that you must put an appropriate application manifest file either next to your executable or embedded as a resource.

You can copy one of the application manifest files that come with the examples.

To embed a manifest file as a resource, you can use the rsrc tool.

IMPORTANT: If you don't embed a manifest as a resource, then you should not launch your executable before the manifest file is in place. If you do anyway, the program will not run properly. And worse, Windows will not recognize a manifest file, you later drop next to the executable. To fix this, rebuild your executable and only launch it with a manifest file in place.

CGo Optimizations

The usual default message loop includes calls to win32 API functions, which incurs a decent amount of runtime overhead coming from Go. As an alternative to this, you may compile Walk using an optional C implementation of the main message loop, by passing the

build tag:

go build -tags walkusecgo

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.