How to Assign a String to a Byte Array in Go

By the end of this page, you will understand how strings and byte arrays relate in Go, how to copy string data into a fixed-size [N]byte array, when a loop is fine, and when the built-in copy function is the better choice.

In Go, a string and a fixed-size byte array like [20]byte are different types with different purposes.

• A string is an immutable sequence of bytes.
• A [20]byte is a fixed-size array that stores exactly 20 bytes.

Because they are different types, you cannot directly assign a string to a byte array.

var arr [20]byte
str := "abc"

// Not allowed
// arr = str

Instead, you need to copy the string's bytes into the array.

A common and idiomatic way is to use Go's built-in copy function:

var arr [20]byte
str := "abc"
copy(arr[:], str)

This works because:

• arr[:] creates a slice view over the whole array.
• copy can copy from a string into a byte slice.

This concept matters because fixed-size byte arrays are often used in:

• binary protocols
• file headers
• network packets
• C interop
• low-level storage formats

In these cases, you often need to place text into a fixed-size field safely and efficiently.

Think of a string as a label containing text, and a [20]byte array as a row of 20 storage boxes.

• The string "abc" contains 3 bytes.
• The array has 20 slots.
• Copying means putting a, b, and c into the first 3 boxes.
• The remaining 17 boxes stay as zero values.

So this:

copy(arr[:], str)

is like saying: take the bytes from the string and place them into the available boxes until you run out of text or space.

Basic syntax

var arr [20]byte
str := "abc"
copy(arr[:], str)

What this does

• arr[:] turns the array into a slice.
• copy copies bytes from str into that slice.
• Since str is shorter than 20 bytes, only the first 3 positions are filled.
• The rest remain 0.

Example: print the array

package main

import "fmt"

func main() {
    var arr [20]byte
    str := "abc"

    copy(arr[:], str)

    fmt.Println(arr)
}

Output:

[97 98 99 0 0               ]

Consider this code:

package main

import "fmt"

func main() {
    var arr [5]byte
    str := "hey"

    n := copy(arr[:], str)

    fmt.Println("copied:", n)
    fmt.Println("array:", arr)
    fmt.Println("first 3 bytes as string:", string(arr[:3]))
}

Step-by-step

1. var arr [5]byte

   • Creates a fixed-size array with 5 bytes.
   • Initial value is:

     [0 0 0 0 0]
     

2. str := "hey"

   • Creates a string containing 3 bytes: h, e, y.

Fixed-width file formats

Some binary or legacy file formats store text in fields of a fixed size, such as 16 or 32 bytes.

var name [16]byte
copy(name[:], "alice")

Network protocol headers

Protocols may define fixed-size byte fields for IDs, names, or command codes.

var header [8]byte
copy(header[:], "PING")

Interfacing with C libraries

When working with C-style structs or memory layouts, you may need fixed byte arrays instead of Go strings.

Embedded or low-level programming

Hardware protocols and packed structures often use fixed-length byte storage.

Database or serialization formats

Some systems represent short text fields as fixed-length byte blocks for predictable layout.

In real Go codebases, developers commonly use copy for this task because it is simple and safe.

Common pattern: copy into fixed buffer

var buf [32]byte
copy(buf[:], value)

Common pattern: validate length first

If truncation is not acceptable, check first:

if len(str) > len(arr) {
    return fmt.Errorf("string too long")
}
copy(arr[:], str)

This is a good example of a guard clause.

Common pattern: zero-padded fields

A fixed array is automatically zero-filled, so copying a shorter string leaves trailing zero bytes.

var field [10]byte
copy(field[:], "id")

This is useful when formats expect null-padded or zero-padded fields.

Common pattern: helper function

In larger projects, developers often wrap this logic in a helper:

   {
     (dst, s)
}

Mistake 1: trying direct assignment

var arr [20]byte
str := "abc"
// arr = str // invalid

Why it fails

A string is not the same type as a byte array.

Fix

copy(arr[:], str)

Mistake 2: forgetting that arrays and slices are different

copy needs a slice as the destination, not the array value directly.

var arr [20]byte
str := "abc"
// copy(arr, str) // invalid

Fix

copy(arr[:], str)

Mistake 3: ignoring truncation

var arr [3]byte
copy(arr[:], "hello")
fmt.Println(string(arr[:]))

Output:

copy(arr[:], str) vs looping

• copy is shorter.
• copy clearly expresses intent.
• A loop is better only if you need custom behavior, such as:

// Copy string into fixed byte array
var arr [20]byte
copy(arr[:], "abc")

// Get number of bytes copied
n := copy(arr[:], "abc")

// Prevent truncation
if len(str) > len(arr) {
    return
}
copy(arr[:], str)

// Convert back using only meaningful bytes
s := string(arr[:n])

Rules

• You cannot assign a string directly to a [N]byte array.
• Use arr[:] to make a slice from the array.
• Use copy(arr[:], str) for idiomatic copying.
• copy truncates if the source is too long.
• Unused array elements remain 0.
• len(str) returns bytes, not necessarily characters.

Good default pattern

var arr [20]byte
 (str) > (arr) {
    
}
(arr[:], str)

Can I assign a Go string directly to a byte array?

No. A string and a fixed-size array like [20]byte are different types.

What is the simplest way to copy a string into [N]byte in Go?

Use:

copy(arr[:], str)

Does copy work directly from a string?

Yes. In Go, copy can copy from a string into a byte slice.

What happens if the string is longer than the array?

Only the bytes that fit are copied. The rest are ignored.

Why use arr[:] instead of arr?

Because copy needs a slice destination, and arr[:] creates a slice over the array.

Is a manual loop wrong?

No. It works fine, but copy is usually cleaner and more idiomatic.

Are strings always one byte per character in Go?

No. Go strings are UTF-8 encoded, so some characters use multiple bytes.

When should I use instead of ?

• Strings in Go — Important because strings are immutable byte sequences.
• Arrays in Go — Directly related since [N]byte is a fixed-size array.
• Slices in Go — Needed because arr[:] creates a slice for copy.
• The copy function in Go — The idiomatic tool for copying bytes and slices.
• UTF-8 and runes in Go — Useful for understanding byte count versus character count.
• Type conversion in Go — Helps explain why string, []byte, and [N]byte are not interchangeable.
• Zero values in Go — Relevant because unused bytes in the array remain 0.