WinFsp: a Windows kernel driver you do not have to program
Windows File System Proxy - FUSE for Windows
At a glance
- What is it?
- A file system platform for Windows whose core is a kernel mode file system driver paired with a user-mode DLL, so application code is written in user space while a driver is still installed, with four API surfaces from Native to .NET, a GPLv3 grant carrying an open source exception, and recent tags that are all 2026 Betas.
- Who is it for?
- WinFsp suits a developer who needs to expose storage or an archive as a Windows drive without writing kernel code, and who is content to install a kernel mode component on the machine. It does not suit a project that cannot tolerate a driver in the image, since the runtime side of the platform is a file system driver even though your code is user mode.
- Can I use it commercially?
- Check first. The repository uses a licence we do not classify automatically, so read its LICENSE file before any commercial use.
- Is it still maintained?
- Yes. The repository received new commits within the last day.
- What is it written in?
- Mainly C, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- winfsp/winfsp9,042 ★ · +136
| Repository | 2026-09-22 | 2026-11-15 |
|---|---|---|
| winfsp/winfsp | 8.9k | 9k |
136 Stars in the last 54 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The core is a kernel driver plus a user-mode DLL
The architecture is two components and understanding the split is what tells you what you are signing up for. The core consists of a kernel mode file system driver and a user mode DLL. The driver interfaces with the Windows kernel and handles all the interactions necessary to present itself as a file system driver. The DLL interfaces with that driver and presents an API you use to handle file system functions, so when an application attempts to open a file, your file system receives an Open call with the necessary information. The pitch is that you write user mode programs with no knowledge of Windows kernel programming, and that is true. The part the phrasing can obscure is that a kernel component is still installed on every machine that mounts your file system. Your code is not kernel code, but its presence is.
The headers come from a checkbox in the installer
Installation is a download and an installer run, with one decision inside it that determines whether you can build anything. The guidance is to download and run the WinFsp installer and, in the installer, select the option to install the Developer files. Those files include the MEMFS sample file system, but also header and library files that let you develop your own user mode file system. So the installer is doing two jobs: installing the runtime platform for end users, and optionally installing an SDK for people writing file systems. A user who is running an existing file system wants the first and can skip the second. A developer who skipped it will find the headers missing at their first compile, which is an avoidable and confusing first hour.
You test by mapping a drive letter to a UNC path
The sample file system is exercised with nothing but standard Windows commands, which tells you how the platform presents itself to the rest of the system. MEMFS is launched from the command line and mapped to a drive letter:
billziss@xps ⟩ ~ ⟩ net use X: \\memfs64\test
The command completed successfully.
billziss@xps ⟩ ~ ⟩ X:
billziss@xps ⟩ X:\ ⟩ echo "hello world" > hello.txt
billziss@xps ⟩ X:\ ⟩ dir
Directory: X:\
Mode LastWriteTime Length Name
---- ------------- ------ ----
-a---- 6/12/2022 5:15 PM 28 hello.txt
billziss@xps ⟩ X:\ ⟩ type hello.txt
hello world
billziss@xps ⟩ X:\ ⟩ cd ~
billziss@xps ⟩ ~ ⟩ net use X: /delete
X: was deleted successfully.Note what is happening. The drive is mapped with a net use against a UNC-style path rather than registered as a local volume, so the shell treats it as a mapped network drive and dir, echo and type all behave normally. The final command unmaps it, which is how you take a file system offline cleanly.
The Launcher is a separate component, and Explorer can use it
Mapping is not something your file system does for itself, and that separation is visible in how testing works. MEMFS, and all file systems that use the WinFsp Launcher as documented in the Service Architecture document, can also be launched from Explorer using the Map Network Drive functionality. The Launcher is documented in the Service Architecture document, which covers WinFsp's facilities for integrating user mode file systems with the Windows shell. For a developer this means two things. Your file system does not need to know how it is presented, which keeps the same implementation usable from a command line, from a service, or from Explorer. And for anyone testing your work, mounting it is a shell operation that needs no knowledge of your binary's arguments.
Four API surfaces, from Native to .NET
The API is offered in four shapes: Native, FUSE2, FUSE3 and .NET. That list is a short version of the porting story. If you already maintain a FUSE file system for Linux or another UNIX-like system, the FUSE2 or FUSE3 surface is likely to be the shortest route, because much of the callback structure you already have maps across. If you write C and want the platform directly, the Native API is there. If you would rather not deal with the FUSE compatibility surface at all, the .NET API means a file system can be written without touching C at all. The consequence for anyone evaluating this is that the choice of API is also a choice of language and of how much of your existing code you can keep, and picking the wrong one is more costly than picking the wrong performance tuning.
GPLv3 with an open source exception, plus a commercial grant
The licensing point is described as flexible, and the specifics are worth reading closely. WinFsp is available under the GPLv3 license with a special exception for Free and Libre and Open Source software, and a commercial license is also available, with a contact address given for details. The exception is the part that matters for open source users, since it is what stops a file system built on this platform from having to adopt the GPL itself. A distributor of closed source software is in the other branch and needs the commercial grant. Note that the repository metadata reports no recognised licence identifier, and the licence text lives in a file named License.txt at the root, so automated tooling reading the repository cannot tell you which grant you are under. For a component with a kernel driver in it, that is worth checking by hand rather than inferring.
The newest tags are 2026 Betas, and the build system is part of the tree
Two things about how this project ships are visible from the metadata. The recent releases are v2.2B5, v2.2B4 and v2.2B3, each labelled as a WinFsp 2026 Beta, so the most recent published artifacts are pre-release builds rather than a stable tag. And the repository carries appveyor.yml, a continuous integration configuration, alongside a .gitmodules file, an asciidoc set under doc for the tutorial, API reference, design, testing and service architecture documents, and separate directories for src, inc, ext, tools, build and tst. That last grouping is the one that tells you something real. Building a component that installs a kernel driver is not a package-manager exercise, which is why the build tree ships with the source.
Editorial conclusion
WinFsp suits a developer who needs to expose storage or an archive as a Windows drive without writing kernel code, and who is content to install a kernel mode component on the machine. It does not suit a project that cannot tolerate a driver in the image, since the runtime side of the platform is a file system driver even though your code is user mode. Before starting, tick the Developer option in the installer or you will have no headers, work out which licence path your distribution needs given the GPLv3 grant carries an open source exception, and decide whether a 2026 Beta tag is acceptable for the machines you ship to.
Frequently asked questions
What is WinFsp used for?
It is a platform for writing custom file systems on Windows as user mode programs, without knowledge of Windows kernel programming. Any information or storage can be presented as a file system and then accessed through the standard Windows file APIs by any application. It is described as similar to FUSE for Linux and other UNIX-like systems.
How do I install WinFsp on Windows?
Download and run the WinFsp installer, and inside it select the option to install the Developer files. Those add the MEMFS sample file system plus the header and library files you need to develop your own user-mode file system; a runtime-only install without that option gives you the platform but nothing to build against.
Is WinFsp free?
It is available under the GPLv3 license with a special exception for Free and Libre and Open Source Software, and a commercial license is also available. The project states it is self-contained with no external dependencies, so there is nothing else to install alongside it.
What is the WinFsp Launcher?
It is documented in the Service Architecture document, which covers WinFsp's facilities for integrating user mode file systems with the Windows shell. File systems that use it, MEMFS among them, can be launched from Explorer through the Map Network Drive functionality as well as from the command line with a net use against the exposed path.
Is WinFsp safe to install?
The platform includes a kernel mode file system driver, so it does install a kernel component. The project claims stability without any known kernel mode crashes, resource leaks or similar problems, and attributes that to its design document and a rigorous testing regime. Support spans Windows 7 through Windows 11 on x86, x64 and ARM64.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/winfsp-winfsp)Star history chart for your README
[](https://hysenlabs.com/projects/winfsp-winfsp)Was this useful?