CLI tool
redis-windows/redis-windows avatar
redis-windows/redis-windows

Redis for Windows: two binaries, two path syntaxes, one local dev tool

Redis 6.0.20 6.2.18 7.0.15 7.2.8 7.4.3 8.0.0 for Windows

4,415 stars342 forksC#Apache-2.0

At a glance

What is it?
This repository compiles official Redis source for Windows and adds RedisService.exe on top of it, a .NET wrapper that converts Windows paths and can install a Windows service. The wrapper is the only entry point that takes a native Windows path, and the project's own disclaimer keeps the whole thing aimed at local development.
Who is it for?
Use this build for a Windows development box, where the Cygwin path rules and the absence of a signed installer cost you little and RedisService.exe saves you an afternoon. Do not put it on a production server: the project's own guidance says to deploy on Linux there, its licence covers this repository and not the official Redis project, and it is not affiliated with Redis Ltd.
Can I use it commercially?
Yes. Apache-2.0 is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 20 days ago.
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.

From daily snapshots

Star history

  • redis-windows/redis-windows4,415 ★ · +107
Star history
Repository2026-09-232026-11-15
redis-windows/redis-windows4.3k4.4k

107 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

Two entry points, and only one accepts a native Windows path

The package is compiled from official Redis source for Windows, and it ships two programs you can start. redis-server.exe is the Redis binary itself, built against the Cygwin runtime. RedisService.exe is a .NET 10.0 wrapper that takes native Windows paths and rewrites them before handing the command line on. The README calls the wrapper the recommended option and says it automatically handles path conversion. That one difference decides the syntax of every other command you type: with the wrapper you write C:\redis-data, with the raw binary you write /cygdrive/c/redis-data. Get it backwards and redis-server.exe will not find your config file, which is the first entry in the project's own FAQ. The wrapper is also the only one of the two that can install itself as a Windows service.

`/cygdrive/c/config/redis.conf` or nothing is found

The build uses the Cygwin runtime, so paths on the command line have to be in Cygwin format:

cmd
redis-server.exe /cygdrive/c/config/redis.conf --dir /cygdrive/d/data --port 6379

The Windows spelling of the same command, redis-server.exe C:\config\redis.conf --dir D:\data, is listed as not supported. The mapping is mechanical:

| Windows | Cygwin | |---------|--------| | `C:\path` | `/cygdrive/c/path` | | `D:\path` | `/cygdrive/d/path` | | `.\data` | `./data` (relative works as-is) |

Inside the config file the rule flips again: use forward slashes in Windows style, so dir C:/redis/data and logfile C:/redis/logs/redis.log are the recommended forms. Three syntaxes in one tool, Cygwin paths on the command line, forward slashes inside redis.conf, and native paths accepted by the wrapper, is the part people get wrong first.

`install` writes a Windows service named Redis by default

RedisService.exe has three commands: install, uninstall and run, with run as the default. A service install takes the config path, the data directory and the port:

cmd
RedisService.exe install -c C:\config\redis.conf --dir D:\data\redis --port 6379
net start Redis
RedisService.exe uninstall

The service name defaults to Redis, which is why the documented start command is net start Redis, and --service-name changes that name if you need more than one instance or a less obvious label. --start-mode takes auto or manual, so a development laptop can be told not to start the database every time it boots. Worth noticing is what the option list does not contain: no flag for a password, and none for a save interval. Those belong in the config file you point at with -c.

The option list is short, and `--dir` is the one that matters

The complete documented option set is small. -c and --config take the config file path, --port the server port, --dir the data directory, --loglevel one of debug, verbose, notice or warning, -f and --foreground run without detaching, --service-name overrides the default Redis name, --start-mode sets auto or manual, and -h and -v print help and version. Because run is the default command, the shortest form of the recommended quick start is RedisService.exe run --foreground, with no config flag at all. Note the asymmetry that catches people out: paths written inside redis.conf use forward slashes, while --dir on the command line takes the native Windows form, because the wrapper converts that argument for you.

Data survives only if `--dir` points where you think it does

Data is saved automatically on shutdown, and the wrapper is careful to pass --dir through so that save lands in the directory you named:

cmd
redis-cli SET mykey myvalue
redis-cli SHUTDOWN
redis-cli GET mykey

The last command is documented as returning "myvalue" after the restart. The project also has an FAQ entry for data lost after a restart, and its three rules are: always specify --dir, shut down gracefully with redis-cli SHUTDOWN or Ctrl+C instead of killing the process, and use the same --dir when you start it again. Killing the process is the failure mode that costs you the dataset, since the write to disk is tied to shutdown.

Program, config and data can sit on three different drives

No location has to share a volume with the others. Program files can live in C:\redis, the config file on D: and the data directory on E:, and each path is passed with its own flag and converted separately:

cmd
RedisService.exe run -c D:\config\redis.conf --dir E:\data\redis --foreground

That matters on Windows in a way it does not on Linux, where a mount point would hold the same arrangement. The same section of the documentation covers why the wrapper exists: converting Windows paths to Cygwin paths is exactly what redis-server.exe will not do for itself. If you would rather avoid that whole class of problem, the wrapper is the way to run it.

The project's own guidance: local development, production on Linux

The disclaimer settles the scope question. This project is not affiliated with, endorsed by or sponsored by Redis Ltd, and the licence provided applies only to this repository, not to the official Redis project. It states that the build is recommended for local development only, that production environments should follow the official Redis guidance and deploy on Linux, and that the project is not responsible for any losses caused by its use. The repository carries an Apache-2.0 licence, and what that licence covers is the wrapper and the build work, not the database being compiled. Read together, the support boundary is a developer machine rather than a server, and that boundary is the author's, stated in advance.

Three tags cut within two days in September 2026

Release tags move quickly here. Redis 8.10.3 for Windows was published on 2026-10-27, and 8.8.3 and 8.6.7 on 2026-09-19, with the last push to the branch on 2026-10-27. Several Redis lines are built rather than one: the description names 6.0.20, 6.2.18, 7.0.15, 7.2.8, 7.4.3 and 8.0.0, so you can match an older client line instead of taking the newest server. The build toolchain is MSYS2 and Cygwin, the service wrapper targets .NET 10.0, and the repository is primarily C#: Program.cs and RedisService.csproj sit at the top level beside CommandLine/, Service/, Native/ and start.bat. README.md has a Simplified Chinese counterpart in README.zh_CN.md.

Editorial conclusion

Use this build for a Windows development box, where the Cygwin path rules and the absence of a signed installer cost you little and RedisService.exe saves you an afternoon. Do not put it on a production server: the project's own guidance says to deploy on Linux there, its licence covers this repository and not the official Redis project, and it is not affiliated with Redis Ltd. Before you rely on it, check two things on the machine you care about: that the Cygwin runtime this build needs is present, and that --dir points at the volume you expect, since data is saved automatically on shutdown.

Frequently asked questions

What is Redis for Windows?

It is Redis compiled from the official Redis source for Windows, plus a .NET 10.0 wrapper called RedisService.exe. The wrapper converts Windows paths to Cygwin paths, can run Redis in the foreground and can install it as a Windows service. The project states it is not affiliated with Redis Ltd.

How do I install Redis for Windows?

The quick start assumes the build is already downloaded and extracted. Then either run redis-server.exe redis.conf, or the recommended RedisService.exe run --foreground. The repository itself contains no installer: what you get is the extracted folder with the binaries.

How do I use Redis for Windows?

Pick one of two documented options. With RedisService.exe you use native Windows paths and it converts them for you. With redis-server.exe directly, every path on the command line must use Cygwin format, such as /cygdrive/c/config/redis.conf. Inside the config file itself, use forward slashes, for example dir C:/redis/data.

Can I use Redis on Windows?

That is what this repository is for, but its own guidance is narrower than the question. It recommends the build for local development only and says production environments should follow the official Redis guidance and deploy on Linux.

Is Redis on Windows slower than Redis on Linux?

The repository publishes no performance figures for either platform, so it does not answer that with numbers. What it does state is that the build is recommended for local development only, and that production should follow the official Redis guidance and deploy on Linux.

Official sources

  1. Issues
  2. License: Apache-2.0
  3. README
  4. redis-windows/redis-windows on GitHub
  5. Releases
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.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/redis-windows-redis-windows.svg)](https://hysenlabs.com/projects/redis-windows-redis-windows)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/redis-windows-redis-windows.svg)](https://hysenlabs.com/projects/redis-windows-redis-windows)

Was this useful?