Skip to content
WampServer logo WampServer
  • Home
  • What is
  • Features
  • Install
  • Compare
  • FAQs
  • Guide
Get WampServer

How to Switch PHP Versions in WampServer

Switch PHP Version in WampServer

WampServer projects can hit PHP compatibility problems when a plugin update fails, an old client site throws errors, or a new project demands a newer runtime — suddenly your local server runs the wrong PHP version. Recreating your setup to fix it is slow and risky. WampServer solves this properly: you can switch PHP version in WampServer from the tray menu in under a minute, without moving a single project file. This guide covers the process, how to add a missing version, and how to confirm the change worked.

Before you start, make sure WampServer is installed and running correctly with the guide to download and install WampServer on Windows. The walkthrough to install WordPress on WampServer shows the kind of project that benefits most from quick version changes.

Why Switch PHP Versions Locally?

PHP evolves quickly, and projects age at different speeds. A maintained WordPress site performs best on a recent release with the latest security and speed fixes. An inherited project or old theme may only run correctly on an earlier release until its code is updated.

Testing across versions also prevents live disasters. Upgrading a live site without testing first is a common cause of white screens and broken checkout pages. Locally, you can raise the version, click through every important page, read the error logs, and fix incompatibilities before visitors see them.

Frameworks set minimum requirements too. A current Laravel or Composer package may refuse an outdated runtime, while debugging an old project may require matching its live server exactly.

PHP Versions Available in WampServer 3.x

WampServer 3.x is designed around switchable components. PHP, Apache, and database versions are managed separately, and extra PHP releases come as add-on packages that plug into your existing installation. You never reinstall WampServer to gain a version — you add it, then select it.

Available versions depend on the add-ons for your build and on the matching Microsoft Visual C++ redistributable packages, since each PHP build relies on a specific runtime library. A missing redistributable is a first cause to check when a version fails to start.

Keep only versions you need. Each one uses disk space, and a short list is faster to work with. For most developers, one older release for legacy work and one current release for new projects covers almost every situation.

Steps to Switch PHP Version in WampServer

Step 1: Start WampServer and Check the Icon

Launch WampServer and wait for the green tray icon, which confirms Apache and your database are running. If the icon is orange or red, fix that first — switching restarts Apache and will fail on a broken setup.

Step 2: Open the PHP Version Menu

Left-click the tray icon to open the main menu. Hover over PHP, then Version. A list of installed versions appears, with the active one marked, so you can confirm what your sites use before changing anything.

Step 3: Select the New PHP Version

Click the version you want. WampServer updates its configuration and restarts Apache automatically. The icon may turn orange briefly, then return to green. Wait until it settles — normally a few seconds — before doing anything else.

Step 4: Verify the Active PHP Version

Confirm the change worked instead of assuming it did:

  1. Open localhost and use the phpinfo link on the WampServer homepage, or create a small phpinfo test file inside C:\wamp64\www.
  2. Read the version at the top of the phpinfo page. It must match the version you selected.
  3. Open your project and check that its pages, dashboard, and login work under the new version.

Step 5: Check Extensions Your Project Needs

Each PHP build has its own extension settings. If a project reports a missing extension after switching, left-click the tray icon, open PHP, then PHP extensions, and enable the required extension for that version — common examples handle images, internationalisation, and encrypted connections. Apache restarts again, so wait for the green icon before retesting.

How to Add a PHP Version That Is Not Listed

If the version you need is missing from the Version submenu, it is not installed yet:

  1. Download the PHP add-on matching your WampServer generation and your 64-bit or 32-bit install. Never mix architectures.
  2. Run the installer while WampServer is closed, and confirm the required Visual C++ redistributable is present.
  3. Start WampServer, open the Version submenu, and confirm the new version appears.
  4. Select it, wait for the green icon, and verify with phpinfo.

Only use official WampServer add-ons. A mismatched package can corrupt your configuration, while the correct one installs cleanly alongside existing versions and projects.

Compatibility Checklist Before Switching

This short checklist prevents most version-change problems.

CheckWhy It Matters
Backup project files and databaseLets you roll back instantly
Check WordPress or framework requirementsConfirms the target version is supported
Note required PHP extensionsEach version stores its own settings
Test login, forms, and checkout locallyCatches incompatibilities early
Review the PHP error log after switchingReveals deprecation warnings to fix

Treat a switch as a small test project, not a casual click. Five minutes of local verification is cheaper than an hour of live repairs.

Common PHP Switching Errors and Fixes

If Apache fails to restart and the icon stays orange, the selected build usually lacks its Visual C++ redistributable, or an enabled extension is broken. Switch back, install the missing runtime, disable recent extensions, and try again.

If phpinfo still shows the old version, the page may be cached or Apache did not fully restart. Use Restart All Services, reload phpinfo in a private window, and check again.

If one project breaks while others work, the problem is almost always project compatibility, not WampServer. Deprecation notices point to code needing updates; fatal errors after a downgrade usually mean the project uses newer features. Match the version to the project and keep a note of each requirement. The wider PHP release history also helps you plan upgrades before a version reaches end of life.

Frequently Asked Questions

Does switching PHP version delete my websites or databases?

No. Your files in C:\wamp64\www and your databases stay untouched. Switching only changes which PHP build Apache uses, and you can switch back anytime.

Can different projects use different PHP versions at the same time?

In a standard setup, one version is active for the whole server at a time. Switch, test the other project, and switch back. Note each project's required version so the routine stays fast.

Why is the PHP version I need missing from the menu?

Only installed versions appear. Install the matching add-on for your build first, restart WampServer, and the version will be listed.

Should I always use the newest PHP version?

Use the newest version your project fully supports. Newer releases bring speed and security improvements, but an untested legacy project can break. Test locally, fix warnings, then upgrade with confidence.

Conclusion

Switching PHP versions takes under a minute once you know the routine: check for a green icon, open PHP and Version in the tray menu, select the release, and verify with phpinfo. Add missing versions through official add-ons and note the right version for each project. With that habit, upgrades become a controlled part of your workflow, not a risk.

WampServer

WampServer simplifies local web development on Windows with essential resources for downloading, installation, configuration, server management, and troubleshooting to ensure a smooth development experience.

Navigation

  • About Us
  • Contact Us
  • Disclaimer
  • Privacy Policy
  • Terms & Conditions
  • Sitemap

© 2026 | WampServer | All Right Reserved

Disclaimer: Not affiliated with WampServer or any other third-party platforms