How to Use System.IO.Path in C# to Manage Paths

System.IO.Path is a static class for manipulating strings that represent file and directory paths.

When working with files (System.IO), many errors don’t come from reading or writing the disk, but from building paths incorrectly.

With backslashes \ on Windows, forward slashes / on Linux, missing dots, relative paths… It’s a minefield.

To prevent our code from being fragile, this class provides tools to combine, split, and normalize paths without fighting with slashes, extensions, and directories.

The Problem with Separators

A quite typical error is writing paths “by hand” ("C:\MyFiles\data.txt"). This is a problem because Windows uses \ and Linux/Mac use /. If you do that, your application will fail on Docker or a Linux server.

// ❌ ERROR: This only works correctly on Windows
string path = "C:\\MyDocuments\\" + fileName;

If you run that code in a Docker container (Linux) or on a Mac, it will likely fail or create files with strange names because Linux expects /.

The Path class solves this by giving us a system constant: Path.DirectorySeparatorChar.

Console.WriteLine($"Your system's separator is: '{Path.DirectorySeparatorChar}'");
// On Windows it will print: '\'
// On Linux it will print: '/'

Combining Paths (Path.Combine)

This is one of the most important functions in the whole class. Instead of concatenating strings with +, we use Path.Combine. This method takes care of adding (or removing) the necessary separators automatically.

string folder = "Users";
string subfolder = "Data";
string file = "config.json";

// ✅ CORRECT WAY
string fullPath = Path.Combine(folder, subfolder, file);
// Result (Windows): "Users\Data\config.json"
// Result (Linux):   "Users/Data/config.json"

// Be careful here:
string path = Path.Combine("C:\\Projects", "C:\\Drivers", "file.txt");
// Result: "C:\Drivers\file.txt" ("Projects" has been omitted)

Path.Join, the Modern Alternative

We also have Path.Join. It is very similar to Combine, but it does not restart the path when it finds a segment with a root. It simply joins the pieces and can be useful in loops where you want to reduce allocations.

Parsing a Path

We often receive a full path (e.g., C:\Photos\2023\vacation.jpg) and need to extract only a part. Path has methods to surgically dissect this string.

Let’s assume the path: string path = @"C:\Work\Report.pdf";

Modifying Paths

Sometimes we don’t want to read a path, but transform it. For example, if we want to change the extension of a file to save it in another format.

ChangeExtension

Changes the extension of a path (or adds it if it doesn’t have one).

string file = "image.bmp";
string newFile = Path.ChangeExtension(file, ".png");
// Result: "image.png"

Absolute and Relative Paths

When we run a program, we sometimes use relative paths like "./config/app.json".

To find out where that actually is on the hard drive, we use GetFullPath.

string relative = "data.txt";
string absolute = Path.GetFullPath(relative);
// Result: "C:\Users\Luis\Projects\MyApp\bin\Debug\net8.0\data.txt"

Temporary and Random Files

Do you need to save a file temporarily and don’t care about the name? Path helps you avoid reinventing the wheel.

// Example: Create a temporary file to process data
string tempFile = Path.GetTempFileName();
// Do things...
File.WriteAllText(tempFile, "Temporary data");
// Delete when done
File.Delete(tempFile);

Invalid Characters

If you allow a user to type a file name, do not assume the input is valid. It may contain prohibited characters like :, *, ?, or <.

To sanitize inputs, we can use GetInvalidFileNameChars():

char[] invalidChars = Path.GetInvalidFileNameChars();
string userName = "Report:Final?.txt";

foreach (char c in invalidChars)
{
    if (userName.Contains(c))
    {
        Console.WriteLine($"Invalid character detected: {c}");
    }
}