Read and write a String from text file: how it works under the hood

How to read and write strings to text files in Swift: looking under the hood

Every developer, regardless of language, sooner or later faces the task: read and write a String from text file. It seems like it couldn't be simpler, right? But in Swift, with its strict type system and safety, this process turns into a fascinating journey into the world of file descriptors, encodings, and file managers. If you've ever wondered, "What actually happens when I call write(to:) or String(contentsOf:)?" — this article is for you.

We won't just show ready-made solutions; we'll break down each step: from finding a file in the sandbox to writing bytes to disk. Buckle up, it's going to be interesting!

Why doesn't Swift just let you write File.write(text)?

Unlike Python or JavaScript, where you can open and write a file in one line, Swift requires explicit specification: what encoding is the string? Where to save (Documents, Caches, Temp)? What to do if the file doesn't exist? This isn't a bug; it's a feature: this approach prevents data leaks and ensures you control every stage.

At the core are three key components:

\n
• FileManager — the "dispatcher" that knows where all your app's folders are located.
\n
• Data — raw bytes. This is what the file system works with.
\n
• String — our high-level representation that must be converted to Data and back.
\n

When you write read and write a String from text file, a chain happens under the hood: String → Data (encoding) → writing bytes to disk (via FileHandle or the Data method).

Practical example: writing a string to a file

Let's start with the simplest and most useful scenario. Imagine you're writing a diary app and want to save a note's text.

import Foundation\n\nlet textToSave = "Hello, world! Today is a great day to learn Swift."\nlet fileName = "my_note.txt"\n\n// 1. Get the path to the Documents directory\nguard let documentsDirectory = FileManager.default.urls(for: .documentDirectory, in: .userDomainMask).first else {\n    fatalError("Failed to get Documents directory")\n}\n\n// 2. Create the full path to the file\nlet fileURL = documentsDirectory.appendingPathComponent(fileName)\n\n// 3. Convert the string to Data (in UTF-8 encoding)\nguard let data = textToSave.data(using: .utf8) else {\n    fatalError("String encoding error")\n}\n\n// 4. Write the data to disk\ndo {\n    try data.write(to: fileURL, options: .atomic)\n    print("File successfully saved at path: \\(fileURL.path)")\n} catch {\n    print("Write error: \\(error.localizedDescription)")\n}

What's happening under the hood here?

\n
• FileManager.default.urls(for:in:) — returns the directory URL. In iOS, this is an isolated sandbox.
\n
• data(using: .utf8) — each character of the string (even emoji) is encoded into one or more bytes according to the UTF-8 standard.
\n
• data.write(to:options:) — a system call that atomically (if .atomic is specified) writes data to a temporary file and then renames it to the target. This protects against data corruption during a crash.
\n

Reading a string from a file: the reverse process

Now that we've saved the note, let's read it back. This is a classic example of read and write a String from text file in action.

import Foundation\n\nlet fileName = "my_note.txt"\n\nguard let documentsDirectory = FileManager.default.urls(for: .documentDirectory, in: .userDomainMask).first else {\n    fatalError("Failed to get Documents directory")\n}\n\nlet fileURL = documentsDirectory.appendingPathComponent(fileName)\n\ndo {\n    // 1. Read the raw