Installing Redis on Mac OS X

redis logo

This post explains how you can install Redis on your Mac OS X system. The instructions will stay pretty much same for any Linux/Unix based system.

If you have Homebrew:

If you don’t have Homebrew:

Grab the latest copy of Redis from this link. At the time of this writing the latest stable release is 3.2.6. Follow the instructions below now.

  • Download Redis. I downloaded redis to my Downloads folder on Mac.
  • First execute the make test command to make sure Redis can complete a clean install on your computer.
  • If no problems were found, continue by executing make on your terminal
  • Next, move these 2 directories into your /usr/bin directory. You’ll need to do this as the sudo user.
  • Now, make a hidden redis directory in your home folder and add a config file called redis.conf into this folder. You can consult the Redis Documentation on what options/parameters you can configure using this conf file.
  • Start up the redis server using:
  • Pingback: Installing Redis on OS X | ZenOnRails()

  • Graeme Houston

    Thank you!

    • narangjasdeep

      You are welcome! 🙂

  • Malkiat Randhawa

    Simple and straight, very helpful, thanks.

  • Luka

    Beautiful! Thank you!

  • Julia Jacobs

    Thank for the great info! I thought I should mention during the make test process I kept getting the Mac OS X admin authorization window (where you have to enter your password for your Mac OS X account) in case anyone else runs into the same issue. I had to enter my password a bunch of times to complete the make test process. I’m sure this would not be necessary if I ran the command with sudo or as root.

    • narangjasdeep

      Thanks for sharing this Julia, I hope this helps other folks who might face a similar issue. I’ll update the post with your findings.

  • Rajan

    Is there difference between installing like this and via homebrew? brew install redis

    • narangjasdeep

      There is no difference as such, the homebrew way is much preferred if you have homebrew installed already. I think i’ll add those steps in too..

  • Mike

    Thanks !

  • Jeremy Leipzig

    great, now how do you turn it off?

    • narangjasdeep

      Please note the 98081 number will be unique to your setup and you’ll get it from the first command.

      • Ян Парамонов

        thx! its only method for stop server on osx>

    • narangjasdeep

      Even better, do:

      ➜ redis-server - stop
      • Jeremy Leipzig

        doesn’t seem to work:
        $ redis-server - stop
        Usage: ./redis-server [/path/to/redis.conf]
        ./redis-server - (read config from stdin)
        ./redis-server --test-memory
        $ redis-server --version
        Redis server version 2.4.17

        • narangjasdeep

          hmmm, I’m on 2.6.14, perhaps just use the kill method I listed in my other comment?

  • gMan

    Helped for me! Thanks!

  • Sinan

    Thank you!

  • Sangram Singh

    Helped for me! Thanks!

  • notfrommississippi

    This was great, saved me a lot of headache, thanks!

  • Shrayas

    Thank you. It worked for me. OSX V10.8.2

    As Julia Jacobs said, it popped up with a lot of auth windows for me too.

  • AndreFigueira

    install brew, then do brew install redis

    • narangjasdeep

      or that. 😉

  • mosinandrey

    Thanks, it’s just what I need

  • Guest

    Github links seem to be broken, “Could not embed GitHub Gist 5628569: API rate limit exceeded for (But here’s the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)”

    • narangjasdeep

      Thank you for bringing this up. I’ve fixed it.

  • Pingback: Building Redis on Mac OS X | The Waldonia Times()

  • Matt Campbell

    brew install redis

    Note that homebrew sort of “namespaces” the location of redis.conf file on Mac OS X something like this:


    …and also…


    On Linux this would be simply: /etc/redis/redis.conf

    • narangjasdeep

      I’ve updated the blog post to include the homebrew instructions.

  • Jitendra Vyas

    how to start redis on startup. I’m on mac

    • Gautam

      place the redis-server in your bash profile .

    • Everton Fraga

      When you install Redis from homebrew, it places a file on ~/Library/LaunchAgents, that has this exact purpose you want. But as you might know, you need to activate it. Here’s how:
      $ launchctl load ~/Library/LaunchAgents/homebrew.mxcl.redis.plist

      and to keep redis from starting along with your system, just run the same command, with *un*load.
      $ launchctl unload ~/Library/LaunchAgents/homebrew.mxcl.redis.plist

  • Alan

    Thank You!

  • Marcus Vinicius Soliva

    Thank You !

  • Shazwi Suwandi

    Simply amazing to have tutorials like this online. You save us all 🙂

  • Michael

    I’ve never trusted using Homebrew because I don’t know what it’s doing. The messages it displays when it installs things make me nervous.

    • verboze

      `brew list redis’ will tell you exactly what it has installed. no need to be nervous. It’s in fact cleaner than installing manually from source because it’s easier to track where things are months down the road when you want to make changes

  • Jaideepsinh Gohil

    Thank you!

  • David Herbold

    Awesome easy. Thank you!

  • दीपक यादव

    worked for me smoothly as per your instructions.Thanks a lot !!

  • Alejandro Ventura

    How to start it manually using the conf file but without having the terminal window opened?

    • Ev

      Using the shell tool called screen, my friend. hit a man screen or google it to know more about.

  • Bruno Oliveira de Alcântara

    I enjoyed this article, the best explanation I’ve seen of it so far

  • MuslimsWithModi

    Thanks man, singh is king 🙂

  • PayneJoe


  • Meenashree Chandan

    In case, not using brew, use /usr/local/bin instead of /usr/bin. But overall, awesome document.

  • Joel

    If you receive an “Operation not permitted” error when attempting to sudo mv, you can either copy them to usr/local/bin or enter recovery mode and disable an element of system integrity protection (not recommend, unless you really know what you’re doing) per the link below.