Introduction

OpenFileDialog is designed for files, not folders. If your real goal is folder selection, the cleanest answer is usually "do not use OpenFileDialog for that". In WinForms, the normal choice is FolderBrowserDialog, and in some modern Windows-only cases you may prefer a more advanced folder picker. The OpenFileDialog workaround exists, but it is still a workaround.

Use FolderBrowserDialog When You Actually Need a Folder

For classic WinForms code, FolderBrowserDialog is the direct tool for the job.

1using System;
2using System.Windows.Forms;
3
4public static class FolderPicker
5{
6    [STAThread]
7    public static void Main()
8    {
9        Application.EnableVisualStyles();
10
11        using var dialog = new FolderBrowserDialog
12        {
13            Description = "Select an output folder",
14            ShowNewFolderButton = true
15        };
16
17        if (dialog.ShowDialog() == DialogResult.OK)
18        {
19            MessageBox.Show(dialog.SelectedPath);
20        }
21    }
22}

That is simpler, clearer, and less fragile than repurposing a file dialog.

The OpenFileDialog Workaround Still Exists

Sometimes you are constrained to OpenFileDialog, usually because of UI consistency or legacy code. In that case, the common trick is to disable file-name validation and provide a dummy file name.

1using System;
2using System.IO;
3using System.Windows.Forms;
4
5public static class FolderPickerWithOpenFileDialog
6{
7    [STAThread]
8    public static void Main()
9    {
10        Application.EnableVisualStyles();
11
12        using var dialog = new OpenFileDialog
13        {
14            ValidateNames = false,
15            CheckFileExists = false,
16            CheckPathExists = true,
17            FileName = "Select folder"
18        };
19
20        if (dialog.ShowDialog() == DialogResult.OK)
21        {
22            string folder = Path.GetDirectoryName(dialog.FileName)!;
23            MessageBox.Show(folder);
24        }
25    }
26}

This works because the dialog lets the user navigate to a folder and "select" a fake file name inside it. You then strip off the fake name and keep the directory path.

Know the Tradeoff

The workaround is acceptable when you understand what it is doing, but it is not the same as native folder selection behavior.

What you gain:

• reuse of the familiar file-dialog UI
• sometimes a more modern-looking shell dialog than FolderBrowserDialog

What you lose:

• semantic clarity
• a true folder-selection API
• some predictability around edge cases and UX details

That is why the best answer is usually still FolderBrowserDialog unless you have a concrete reason to avoid it.

Keep the User Experience Clean

No matter which dialog you choose, a few details matter:

• set a clear description or title
• initialize the dialog to a sensible starting directory
• handle cancel cleanly
• store the last selected path if the workflow repeats

Example with an initial folder:

1using var dialog = new FolderBrowserDialog
2{
3    Description = "Select the source folder",
4    SelectedPath = @"C:\Work"
5};

Those small touches improve usability more than arguing about the dialog class name.

If You Need a More Modern Folder Picker

Some applications use newer Windows shell APIs or helper libraries for a more modern folder-picking experience. That can be a good choice in Windows-only desktop apps, but it is separate from the question of whether OpenFileDialog itself supports folders. By default, it does not.

So the practical answer remains:

• use the dedicated folder dialog when possible
• use the OpenFileDialog trick only when you must

Common Pitfalls

• Assuming OpenFileDialog has native folder-selection support.
• Using the workaround without understanding why the fake file name is needed.
• Forgetting to call Path.GetDirectoryName and accidentally keeping the placeholder file name.
• Choosing OpenFileDialog just because it looks nicer, even when FolderBrowserDialog is a better semantic fit.
• Not handling cancel and null-path cases cleanly.

Summary

• 'OpenFileDialog is for files, not folders.'
• For WinForms folder selection, FolderBrowserDialog is usually the correct choice.
• An OpenFileDialog workaround is possible with ValidateNames = false and a dummy file name.
• The workaround is useful in legacy or UI-constrained cases, but it is still a workaround.
• Choose the dialog that matches the user action instead of forcing a file dialog into folder semantics.