Buffer allocation and encoding in Node.js - Step-by-Step Execution

Concept Flow - Buffer allocation and encoding

Start

↓

Allocate Buffer

↓

Write Data with Encoding

↓

Read or Use Buffer

↓

End

This flow shows how Node.js allocates a buffer, writes data with a specific encoding, then reads or uses the buffer.

Execution Sample

Node.js

const buf = Buffer.alloc(5);
buf.write('Hi', 'utf8');
console.log(buf);
console.log(buf.toString('utf8'));

Allocates a 5-byte buffer, writes 'Hi' in UTF-8 encoding, then prints the buffer and its string form.

Execution Table

Step	Action	Buffer Content (hex)	Buffer Content (string)	Notes
1	Allocate buffer of length 5	00 00 00 00 00		Buffer initialized with zeros
2	Write 'Hi' with utf8 encoding	48 69 00 00 00	Hi	'H' = 0x48, 'i' = 0x69, rest zeros
3	Print buffer object	<Buffer 48 69 00 00 00>		Shows raw bytes in hex
4	Convert buffer to string utf8	48 69 00 00 00	Hi	Decodes entire buffer; null bytes (\u0000) included but non-printable in console
5	End			Process complete

💡 Buffer allocated fixed size; write fills bytes; toString decodes entire buffer by default (null bytes included)

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 4	Final
buf	undefined	<Buffer 00 00 00 00 00>	<Buffer 48 69 00 00 00>	<Buffer 48 69 00 00 00>	<Buffer 48 69 00 00 00>

Key Moments - 3 Insights

Why does the buffer show zeros after the written characters?

Because the buffer was allocated with a fixed size of 5 bytes, and only the first 2 bytes were written with 'Hi'. The remaining 3 bytes remain zero as shown in step 2 of the execution table.

Why does buf.toString('utf8') output 'Hi' and not include the trailing zeros?

The toString method decodes the entire buffer as UTF-8, resulting in 'Hi\u0000\u0000\u0000'. Null bytes (\u0000) are non-printable, so they do not visibly appear in console output (step 4).

What happens if you write a string longer than the buffer size?

Only the bytes that fit in the allocated buffer are written; the rest are ignored. This prevents buffer overflow but truncates the string.

Visual Quiz - 3 Questions

Look at the execution table, what is the buffer content in hex after writing 'Hi'?

A 00 00 00 00 00

B 48 69 00 00 00

C 48 69 48 69 00

D 00 48 69 00 00

💡 Hint

Check step 2 in the execution table for buffer content after write

At which step does the buffer get allocated with zeros?

A Step 2

B Step 3

C Step 1

D Step 4

💡 Hint

Look at the first step where the buffer is created

If you write 'HelloWorld' into the 5-byte buffer, what happens?

A Buffer contains 'Hello' and ignores the rest

B Buffer expands automatically to fit all

C Buffer throws an error

D Buffer contains 'World'

💡 Hint

Recall buffer size is fixed at allocation (step 1) and write truncates excess

Concept Snapshot

Buffer.alloc(size) creates a fixed-size buffer filled with zeros.
Use buf.write(string, encoding) to write data into the buffer.
Writing beyond buffer size truncates the string.
buf.toString(encoding) decodes the entire buffer as string by default; null bytes become \u0000.
Buffers hold raw bytes, useful for binary data handling in Node.js.

Full Transcript

This lesson shows how Node.js buffers are allocated and used. First, a buffer of fixed size is created with Buffer.alloc, filled with zeros. Then, writing a string like 'Hi' with UTF-8 encoding fills the first bytes of the buffer. The rest remain zero. When printing the buffer, you see the raw bytes in hex. Converting the buffer to a string decodes all bytes; trailing null bytes are included but invisible when printed. Writing a string longer than the buffer size only writes what fits, truncating the rest. This helps manage binary data safely and efficiently.