Install WordPress Locally in Windows

Posted on 26. Aug, 2009 by Alex Denning in Quick Tips

There are plenty of articles around about installing WordPress locally, but the other week when I wanted to do it, I couldn’t find out how to do it. How awful! Today I’m going to walkthrough installing WordPress locally on Windows as I don’t have a Mac. Yet. I digress.

Install Wamp Server

We’re going to be using something called Wamp Server. Download it and install it. When installing, ignore the SMTP setup screen, below as you don’t really need it.

With that done, click launch WAMP server. Next, with WAMP installed, click ‘Start’, ‘Computer’, ‘Local Disc (C)’, ‘wamp’ and then ‘www’. This is where ‘stuff’ goes. In our case, ‘stuff’ is WordPress. Download the latest version from WordPress.org. Unzip the file, copy and paste the contents into the www folder we just navigated to. Here comes the installation bit. Make sure that your WAMP server is online – in your browser to to /localhost/phpmyadmin. If it is online then you’ll see something like the below, but if you don’t, go into all programs and under ‘WampServer’ click ‘start’.

Next step is to create a new MySQL Database. Fill in the box above with ‘WordPress’ and click create. With that done, close phpMyAdmin.

Now we’re onto the home straight. Go back to your www file and open the wp-config-sample file. Then fill in the fields with the details below.

// ** MySQL settings - You can get this info from your web host ** //
/** The name of the database for WordPress */
define('DB_NAME', 'WordPress');

/** MySQL database username */
define('DB_USER', 'root');

/** MySQL database password */
define('DB_PASSWORD', '');

/** MySQL hostname */
define('DB_HOST', 'localhost');

Then save the wp-config-sample file as wp-config.php and you’re done! Navigate to /localhost/, follow the instructions and you’re done! Simple, no?

This post is a slight heard start to next week’s ‘A Beginner’s Guide to WordPress Theme Development’ week; subscribe by RSS to make sure you catch it!

Related posts:

  1. How To Stop An Ethical Hacker Breaking Into Your WordPress Site

Follow on Twitter! Subscribe!
Alex's Gravatar

Alex Denning is the founder of WPShout. A WordPress developer from London, Alex co-founded WPShift at the start of 2010 where he sells awesome WordPress themes.

You can find Alex on Twitter and at AlexDenning.com.

9 Responses to “Install WordPress Locally in Windows”

  1. Rarst

    26. Aug, 2009

    There are also some stacks that come with WP pre-installed or with simplified installation. Perosnally I use MoWeS cause it’s portable. Also heard good feedback about BitNami.
    .-= Rarst´s last blog ..Remove and fix Layered Service Provider (LSP) entries =-.

    Reply to this comment
  2. BYurick

    27. Aug, 2009

    That’s definitely the shortest “How To” I think I’ve ever seen. Short and simple is usually best anyway!
    .-= BYurick´s last blog ..WordPress Security Tip #3 =-.

    Reply to this comment
  3. emrah gunduz

    20. Oct, 2009

    There is also Mowes Portable ( http://www.chsoftware.net/en/useware/mowes/mowes.htm ). A great portable apache + mysql server solution for Windows. You can keep everything in a usb stick, move, copy all the files from hard disk to disk, or even after a format, just run the executable : you won’t need to install anything.

    Mowes also gives you great choices for what you wantto add to your portable server solution. They all come in single packages. Including phpmyadmin, ImageMagick, Drupal, Joomla, WordPress, etc…

    While downloading you can select which packages you want with the executable. After downloading, Mowes will extract the packages once, and everything will be ready for use.

    You mush definitely check that out, too.
    .-= emrah gunduz´s last blog ..Maxscript : Auto Mirror Selected Using a Specific/Picked Object =-.

    Reply to this comment
  4. Steve Warriner

    06. Mar, 2010

    What is the difference between WAMP and MAMP (other than inverted 1st letter)?

    Really, I downloaded WAMP the other day and went to install it and follow the instructions here to realize…the obvious.

    Any recommendation which s better?

    Thanks
    -JEDs

    Reply to this comment
    • Steve Warriner

      06. Mar, 2010

      ok, via wikipedia:

      W=windows
      M=Mac

      So, why are you using MAMP to install worpress locally on windows?

      -JEDs

      Reply to this comment
      • Alex Denning

        07. Mar, 2010

        Erm, I’m not.

        We’re going to be using something called Wamp Server.

        Reply to this comment
        • Steve Warriner

          12. Mar, 2010

          Alex, my apologies. acronym overload I guess (extracting foot from mouth).

          If I can try to add something to this thread, I have run into 2 things:

          First, the www directory has its own index file, prior to loading worpress into it, which also has an index. I renamed the wordpress index file for now, as the wamp index is localhost.

          The wordpress index file will be needed on the host to load the wordpress environment and theme.

          Do I have that straight so far? (really hoping you will answer)

          Second, wamp will not work if anything is using port 80, lots of stuff online about this. Skype and microsoft IIS look to be the main culprits.

          IIS was my problem, but after asurrance it could be disabled (from the wamp forum), I am finally in to localhost.

          Thanks,

          -JEDs

          Reply to this comment

Trackbacks/Pingbacks

  1. [...] The only other quick thing we need to do is install WordPress locally. You can find how to do that here.Part 2Creating a basic themeFirst off, the style.css. This is our stylesheet. This isn’t a design [...]

Leave a Reply

Please use your real name when commenting. Wrap code in <code> tags and make sure HTML is encoded. You can use regular HTML like <a href="... etc.

Get yours questions answered quicker

If you're using this post for paid work and have a question of any complexity then please ask at WPQuestions where you'll get a prompt response.