Go Error — Undefined Variable

What Does This Error Mean?

A Go 'undefined' error means your code references a variable, function, or type that the compiler has never seen. Go checks every name at compile time. If it cannot find a declaration for the name, it refuses to build. This is usually caused by a typo, a missing import, or using a variable outside the block where it was declared. Fix it by checking the name spelling, adding the correct import, or moving the variable declaration to the right place.

Affected Models

Go 1.0 and later
All Go versions
go build, go run, go test

Common Causes

Typo in a variable or function name — Go is case-sensitive
Using a variable declared inside an if or for block outside of that block
Forgetting to import the package that provides the function or type
Declaring a variable with := inside a block without realizing the outer variable is separate
Referencing an exported identifier from another package without the package prefix

How to Fix It

Read the error message to find the exact undefined name. Compare it character-by-character to your code.

Go is case-sensitive. fmt.Println and fmt.println are different — the second does not exist.
If it is a package function like fmt.Println or os.Exit, check your import block at the top of the file. Add the missing import.

Use the Go import path: import "fmt" for the fmt package. IDEs like VS Code add imports automatically.
If the variable is declared inside a block (if, for, func), remember it only exists inside that block. Move the declaration outside if needed.

Declare the variable before the block with var x int or x := 0, then assign it inside the block.
If you are using a name from another package, prefix it with the package name: mypackage.MyFunction() not just MyFunction().

Only exported names (starting with a capital letter) can be used from outside the package.
Run goimports or use your IDE's auto-import feature to automatically add missing imports and remove unused ones.

goimports is part of the Go toolchain. It saves time by managing imports for you.

When to Call a Professional

Undefined errors always prevent compilation. They are almost always caused by typos or missing imports. The compiler message tells you the exact name it could not find and the line number. Fix it before moving on — Go will not build any part of the program while this error exists.

Frequently Asked Questions

Why does Go not allow unused variables?

Go refuses to compile if you declare a variable but never use it. This is intentional. Unused variables are often signs of leftover code, bugs, or forgotten logic. By making them a compile error, Go keeps codebases clean and prevents subtle mistakes.

I declared the variable — why does Go still say it is undefined?

Most likely the variable is declared in a different scope (inside a block) than where you are using it. In Go, curly braces {} create a new scope. Variables declared inside only exist there. Declare the variable before the block where it is assigned.

What is the difference between undefined and undeclared in Go?

In practice, both mean the same thing: Go cannot find a declaration for that name. The compiler may use slightly different wording depending on what kind of name it is. Either way, the fix is the same: declare the variable, add the import, or fix the typo.