Skip to main content
The Bun.file and Bun.write APIs documented on this page are heavily optimized and represent the recommended way to perform file-system tasks using Bun. For operations that are not yet available with Bun.file, such as mkdir or readdir, you can use Bun’s nearly complete implementation of the node:fs module.

Reading files (Bun.file())

Bun.file(path): BunFile Create a BunFile instance with the Bun.file(path) function. A BunFile represents a lazily-loaded file; initializing it does not actually read the file from disk.
The reference conforms to the Blob interface, so the contents can be read in various formats.
File references can also be created using numerical file descriptors or file:// URLs.
A BunFile can point to a location on disk where a file does not exist.
The default MIME type is text/plain;charset=utf-8, but it can be overridden by passing a second argument to Bun.file.
For convenience, Bun exposes stdin, stdout and stderr as instances of BunFile.

Deleting files (file.delete())

You can delete a file by calling the .delete() function.

Writing files (Bun.write())

Bun.write(destination, data): Promise<number> The Bun.write function is a multi-tool for writing payloads of all kinds to disk. The first argument is the destination which can have any of the following types:
  • string: A path to a location on the file system. Use the "path" module to manipulate paths.
  • URL: A file:// descriptor.
  • BunFile: A file reference.
The second argument is the data to be written. It can be any of the following:
  • string
  • Blob (including BunFile)
  • ArrayBuffer or SharedArrayBuffer
  • TypedArray (Uint8Array, et. al.)
  • Response
All possible permutations are handled using the fastest available system calls on the current platform.
To write a string to disk:
To copy a file to another location on disk:
To write a byte array to disk:
To write a file to stdout:
To write the body of an HTTP response to disk:

Incremental writing with FileSink

Bun provides a native incremental file writing API called FileSink. To retrieve a FileSink instance from a BunFile:
To incrementally write to the file, call .write().
These chunks will be buffered internally. To flush the buffer to disk, use .flush(). This returns the number of flushed bytes.
The buffer will also auto-flush when the FileSink’s high water mark is reached; that is, when its internal buffer is full. This value can be configured.
To flush the buffer and close the file:
Note that, by default, the bun process will stay alive until this FileSink is explicitly closed with .end(). To opt out of this behavior, you can “unref” the instance.

Directories

Bun’s implementation of node:fs is fast. Use node:fs for working with directories in Bun.

Reading directories (readdir)

To read a directory in Bun, use readdir from node:fs.

Reading directories recursively

To recursively read a directory in Bun, use readdir with recursive: true.

Creating directories (mkdir)

To recursively create a directory, use mkdir in node:fs:

Benchmarks

The following is a 3-line implementation of the Linux cat command.
cat.ts
To run the file:
terminal
It runs 2x faster than GNU cat for large files on Linux.
Cat screenshot

Reference