Golang Variable Naming Convention Guideline and TIPs

Written by - Tuan Nguyen
Reviewed by - Deepak Prasad

Introduction to Golang Naming Convention

Welcome to the fascinating world of variables in Golang (Go)! In this tutorial, we will embark on a comprehensive journey to understand the golang variable naming convention and unveil the secrets behind effective and meaningful variable names in Go programming.

Variables are fundamental building blocks in programming. They act as containers that store data values which can be manipulated and accessed throughout the code. In Golang, the naming convention of these variables holds significant importance. A well-named variable can make the code more readable, understandable, and maintainable. This means that when you or someone else reads the code, the purpose and usage of each variable are clear, making the code easier to work with and modify.

In the following sections, we will cover various aspects of golang naming convention, exploring topics like basic variable naming, constant variable naming, function and parameter naming, among others. We'll dive deep into conventions for naming various types of variables, such as local and global variables, constant variables, and even dive into the naming of packages and error variables. The use of CamelCase and snake_case in Go, the naming of boolean variables, handling abbreviations and acronyms, and common mistakes and pitfalls will also be illuminated. Additionally, we will also explore the supportive tools and automation, like linters and formatters, which can assist you in adhering to the best naming practices.

So, buckle up for an enlightening exploration of best practices and conventions that will elevate the clarity, effectiveness, and professionalism of your Go code!


Golang Variable Naming Conventions

In Golang, a set of rules and guidelines steer the naming of variables, functions, packages, and other identifiers. These rules, fundamental to the golang naming convention, optimize code readability and maintenance.

  • Names should be concise yet meaningful.
  • Exported identifiers should start with uppercase letters.
  • Unexported identifiers should start with lowercase letters.

Basic syntax involves simple yet descriptive names, making use of CamelCase for multiple words, and avoiding the use of underscores (_) in the names, except in special circumstances.


Basic Variable Naming

In the realm of golang variable naming convention, basic variable naming holds a pivotal place, acting as the foundation upon which other naming conventions are built. This section emphasizes two main kinds of variables: local and global.


Local Variables

Local variables are defined within functions and are only accessible within those functions. When naming local variables, brevity is appreciated, but the names should still be descriptive enough to convey the variable’s purpose. The golang naming convention suggests using shorter names for local variables, keeping them concise yet meaningful.

package main

import "fmt"

func main() {
    // A well-named local variable
    userName := "JohnDoe"
    fmt.Println("User Name:", userName)

Local variables like localVar and userName are named concisely and are used within the scope of functions.


Global Variables

Global variables, on the other hand, are accessible throughout the package in which they are declared. Given their wider scope of visibility and longevity, it’s imperative to choose names that are descriptive and clarify the variable's role and usage within the package. The convention also dictates that the names of global variables should start with uppercase letters if they are to be exported, meaning they will be accessible outside of the package.

package main

import "fmt"

// Exported global variable
var UserName string 

func init() {
    UserName = "JohnDoe"

func main() {
    // Accessing the global variable
    fmt.Println("User Name:", UserName)

Global variables like GlobalVar and UserName are capitalized, signifying that they can be exported and accessed outside of the package.


Constant Variable Naming

Constants in Go are immutable values which, once defined, cannot be altered during the execution of the program. They can be either exported or unexported, depending on whether or not they should be accessible outside the package they are defined in. Adhering to the golang variable naming convention is essential for consistent and readable code.

Unexported Constants:

Unexported constants are accessible only within the package they are defined. Their names typically start with a lowercase letter.

package main

import "fmt"

const pi = 3.14159

func main() {
    fmt.Println("Value of pi:", pi)

Exported Constants:

Exported constants can be accessed from outside the package they are defined in. Following the golang naming convention, their names start with an uppercase letter.

package main

import "fmt"

const MaxEmployees = 1000

func main() {
    fmt.Println("Employee Count:", MaxEmployees)


Function and Parameter Naming

Function Names

Function names in Go should be descriptive and follow PascalCase if they are exported, and camelCase for unexported functions, adhering to the golang naming convention.

  • Exported Function: func CalculateInterest() {}
  • Unexported Function: func calculateInterestPrivate() {}

Parameter Names and Return Values

Parameter names should be in camelCase and be descriptive enough to understand the purpose of the parameter in the function.

func printEmployeeDetails(employeeID int, employeeName string) {}

Return Values

Named return values should also be in camelCase and have a descriptive name, elucidating the kind of value the function returns.

func getEmployeeDetails() (employeeName string, employeeAge int) {}

Here is an example:

package main

import "fmt"

// Function with well-named parameters and return value
func add(x int, y int) int {
    sum := x + y
    return sum

func main() {
    result := add(2, 3)
    fmt.Println("Sum:", result)

In these examples:

  • Constants and function names adhere to the visibility rules of Go, using uppercase for exported identifiers.
  • Consistent and meaningful naming conventions are used, following the best practices of golang naming convention.


Package Naming

In the vast landscape of golang variable naming convention, package naming holds a position of notable significance. Packages are a way of organizing your project, and the names you choose should succinctly convey the package’s purpose.

Package-Level Variables:

Package-level variables are accessible throughout the entire package. The golang naming convention emphasizes clarity and scope visibility in naming these variables.

package shapes

// Package-level variable
var Description = "This package provides basic shape operations."

func GetDescription() string {
    return Description

Visibility (Exported/Unexported Variables):

In Go, exported variables or functions start with an uppercase letter, making them accessible outside their package.

package shapes

// Exported variable
var Version = "1.0"

// Unexported variable
var author = "Jane Doe"


Structs and Interfaces Naming

Struct Naming

Struct names should be in PascalCase, which is in line with the golang naming convention, to ensure they are exported and usable outside the package.

type EmployeeStruct struct {
    EmployeeID   int
    EmployeeName string

Interface Naming

Interfaces should also follow the PascalCase naming convention. A common practice in Go is to end the interface names with "er" to indicate the action performed by the interface.

package main

// Interface representing a talker
type Talker interface {
    Talk() string

// Implementing the interface
type Human struct{}

func (h Human) Talk() string {
    return "Hello!"


Error Variable Naming

Error Constants

Error constants are typically prefixed with Err to make it clear that they represent error types. They should follow the PascalCase convention as they are exported and used outside the package.

const ErrInvalidInput = errors.New("Invalid input")

Error Variables

Error variables, like error constants, should be descriptive and prefixed with Err. They clarify the nature of the error, adhering to the golang naming convention.

var ErrNotFound = errors.New("Item not found")


CamelCase, Snake_Case and PascalCase in Go

CamelCase and snake_case are two popular naming conventions used in programming, and each has its specific use cases in Go programming as well.

CamelCase in Go

CamelCase concatenates words without spaces, and each word (or abbreviation) begins with a capital letter. In Go, CamelCase is commonly used for naming variables, functions, constants, and struct types, especially when they are exported or global. CamelCase helps in maintaining readability while adhering to the golang variable naming convention.


  • Variable: employeeSalary
  • Function: CalculateTotalAmount()
  • Struct: type EmployeeDetails struct {...}

Snake_Case in Go

Snake_case concatenates words by using underscores (_) to replace spaces. This naming convention is less commonly used in Go compared to CamelCase. However, snake_case might appear in filenames, directory names, or in specific cases where it's a convention, like in SQL-related operations.


  • Filename: employee_details.go
  • SQL-related: employee_id

PascalCase in Go

PascalCase is a subset of CamelCase. In PascalCase, the first letter of the identifier is capitalized. It's a common practice in Go to use PascalCase for naming exported variables, constants, functions, and types (structs and interfaces), ensuring they are accessible from other packages.


  • Exported Variable: TotalAmount
  • Exported Function: GetEmployeeDetails()
  • Struct: type DepartmentInfo struct {...}

Using PascalCase for exported identifiers aligns with the visibility rules in Go, making the code consistent and readable.


Abbreviations and Acronyms

In programming, abbreviations are often used to keep variable names concise. In Go, if you use an abbreviation, it should be in uppercase, especially if it’s a well-known abbreviation. Following a consistent rule for abbreviation usage is crucial to maintain clarity and consistency, adhering to the golang variable naming convention.

Handling Common Abbreviations:

Common abbreviations may be used in names, but they should be consistent throughout the code.

// Using abbreviation in function name
func getHTMLContent() string {
    return "<html>Content</html>"

Acronyms in Variable Names:

Acronyms are similar to abbreviations but formed from the initial letters of other words and pronounced as a single word. In line with the golang naming convention, acronyms in variable or function names are usually all in uppercase, or the first letter is uppercase if they are at the beginning of the name.

// Using acronym in variable name
var URLLink = "http://example.com"


Boolean Variable Naming

Boolean variables typically hold true or false values and play a pivotal role in decision-making structures. Naming them correctly, according to the golang variable naming convention, is crucial for code readability and understanding the logic flow.

Best Practices:

  • The name should clearly indicate the condition being evaluated or the status being represented.
  • It's beneficial if the name includes a verb or a question form to make it evident that it holds a boolean value.


  • isUserLoggedIn
  • hasAccess
  • canEdit

Common Mistakes:

Avoid using generic or ambiguous names that do not provide a clear understanding of the variable’s purpose or the condition it's holding.

// Avoid
var flag bool = false

// Prefer
var isFeatureEnabled bool = false


Temporary Variable Naming

Temporary variables are often used for short-term operations like loop counters and iterators. The golang variable naming convention advises keeping these names short and relevant to their usage.

Short-Term Variables:

Short-term variables, such as those used temporarily in a function or block, should have concise names, often one or two characters long.

// Temporary variable in a calculation
tempResult := x + y

Loop Counters and Iterators:

Loop counters and iterators usually have short names like i, j, k, etc. They are short-lived and used specifically for iteration.

// Using loop counter variables
for i := 0; i < 10; i++ {


Import Naming Conventions

Following the golang variable naming convention when importing packages can help in organizing the code and avoiding conflicts. This is especially important when dealing with package aliases and conflict resolution.

Package Import Aliasing:

Sometimes, it may be necessary to alias a package upon importing it to avoid naming collisions or for simplicity.

package main

import (
    f "fmt" // aliasing fmt package as f

func main() {
    f.Println("Hello, Golang naming conventions!")

Conflict Resolution:

When two packages have conflicting names, you can use aliasing to resolve the conflict, adhering to the golang naming convention.

import (
    sql "database/sql"
    mysql "github.com/go-sql-driver/mysql"


Frequently Asked Questions (FAQs)

What is the significance of Golang naming conventions?

Golang naming conventions are essential because they introduce a standardized way of naming variables, functions, packages, and other identifiers in your code. They enhance the readability, maintainability, and understanding of the code, promoting better collaboration and fewer errors in a team environment.

How should I name variables in Golang?

Variables should be named in camelCase and should be descriptive. For instance, employeeName and totalAmount. Single-letter variables, like i or x, are typically used for short-lived variables, such as loop counters.

How should exported and unexported identifiers be named?

Exported identifiers (those that need to be accessible outside their package) should start with a capital letter, making them PascalCase, e.g., Employee. Unexported identifiers (those only accessible within their package) should start with a lowercase letter, e.g., employeeDetails.

What are the conventions for naming constants in Golang?

Constants should be named using PascalCase if they are exported, e.g., MaxValue. Unexported constants can be in camelCase, e.g., maxValue.

What naming convention is followed for functions and methods in Golang?

Function names should be descriptive and in PascalCase if they are exported, e.g., CalculateTotal(). Unexported functions should be named in camelCase, e.g., calculateTotal().

How should I handle acronyms and abbreviations in identifiers?

Acronyms and abbreviations should maintain their case, e.g., parseHTML, userID. In exported identifiers, keep the acronym uppercase, e.g., HTMLParser, UserID.

How do I manage package naming in Golang?

Package names should be in lowercase without underscores or mixed caps and be descriptive, e.g., net, http. Avoid using reserved words.

How should error variables and constants be named?

Error variables and constants typically begin with Err or err, and they follow the convention of error handling, e.g., ErrInvalidInput or errNotFound.

What is the guideline for naming temporary and short-lived variables?

Temporary variables can have short, generic names such as tmp, temp, or single-letter names like t, especially if their usage is limited and clear in context.

How should I handle package import naming and aliasing?

When aliasing imports, the alias should reflect the package’s purpose or content, e.g., f "fmt". Aliasing can also help avoid naming conflicts in the code.



In the realm of Go programming, adherence to the golang variable naming convention is instrumental in crafting code that is efficient, readable, and maintainable. Throughout this tutorial, various aspects of the golang naming convention have been elucidated with pertinent examples, fostering a robust understanding of naming variables, constants, functions, packages, and more.

Summarizing Key Takeaways:

  • Consistency and clarity are paramount in naming.
  • Utilize CamelCase for variables and function names, ensuring exported names start with uppercase letters.
  • Employ meaningful and descriptive names, enhancing code readability.

Additional Resources and References:

  • For an in-depth understanding, refer to the official Go documentation .
  • Various community-driven platforms like Go by Example also offer invaluable insights into the world of Go programming.


Tuan Nguyen

He is proficient in Golang, Python, Java, MongoDB, Selenium, Spring Boot, Kubernetes, Scrapy, API development, Docker, Data Scraping, PrimeFaces, Linux, Data Structures, and Data Mining. With expertise spanning these technologies, he develops robust solutions and implements efficient data processing and management strategies across various projects and platforms. You can connect with him on LinkedIn.

Categories GO

Can't find what you're searching for? Let us assist you.

Enter your query below, and we'll provide instant results tailored to your needs.

If my articles on GoLinuxCloud has helped you, kindly consider buying me a coffee as a token of appreciation.

Buy GoLinuxCloud a Coffee

For any other feedbacks or questions you can send mail to admin@golinuxcloud.com

Thank You for your support!!

2 thoughts on “Golang Variable Naming Convention Guideline and TIPs”

  1. Hi Tuan. I found this to be very helpful. I’ve had a hard time finding suggestions on specific variable naming conventions for Go, which is funny because most of what we name are variables. . . Anyway, small error, your example for Camel Case and Pascal Case are the same. Camel case is:

       VariableName := "Harry Potter" 
       VariableAge := 20

    but should be:

       variableName := "Harry Potter" 
       variableAge := 20

Leave a Comment