What are Buffers in Node.js?

Question

Accepted Answer

A **Buffer** is Node's way to handle **raw binary data** — a fixed-length sequence of bytes stored outside the V8 heap. Since JavaScript strings are for text (Unicode), Buffers exist to work with binary: file contents, network packets, images, encryption, etc.

## Why Buffers exist

```text
JavaScript strings → text (UTF-16). Can't cleanly represent arbitrary bytes.
Buffers → raw bytes (0–255 each). For binary data that isn't text.
```

When you read a file or receive network data, it arrives as bytes — a Buffer — which you can then decode to a string if it's text, or process as binary if it's not.

## Creating and using Buffers

```js
const buf = Buffer.from("Hello");          // from a string → bytes
const buf2 = Buffer.from([72, 105]);       // from byte values → "Hi"
const buf3 = Buffer.alloc(10);             // 10 zero-filled bytes

buf.length;          // 5 (bytes, not characters)
buf.toString("utf8"); // "Hello" — decode back to text
buf.toString("hex");  // "48656c6c6f"
buf.toString("base64"); // "SGVsbG8="
buf[0];              // 72 — access individual bytes
```

## Where Buffers show up

```js
// file reads without an encoding return a Buffer
const data = await fs.promises.readFile("image.png"); // Buffer (binary)
const text = await fs.promises.readFile("file.txt", "utf8"); // string (decoded)

// streams emit Buffer chunks
req.on("data", (chunk) => { /* chunk is a Buffer */ });

// crypto, compression, network protocols all work with Buffers
crypto.randomBytes(16); // a Buffer of 16 random bytes
```

If you read a file *without* specifying an encoding, you get a Buffer; specify `"utf8"` and Node decodes it to a string for you.

## A subtle point: bytes vs characters

```js
Buffer.from("café").length; // 5 (é is 2 bytes in UTF-8) — NOT 4 characters
```

Buffer length is in **bytes**, which can differ from the number of characters for multi-byte (non-ASCII) text — relevant when slicing binary data.

## Why it matters

Buffers are how Node handles all **binary data**, which is unavoidable in server work: reading non-text files, processing streams, network protocols, cryptography, image/file uploads, and compression.

Understanding that I/O fundamentally deals in bytes (Buffers) — and how to convert between Buffers and strings with the right encoding — is essential whenever you go beyond plain text, and it underpins streams, the file system, and crypto.