Rumors that PHP is dead keep recurring on programming forums, leaving many beginner developers and site owners hesitant to choose a backend technology or delaying server updates. This confusion is compounded by the fact that PHP releases advance every year with major changes, while many production applications remain stuck on older branches that are beginning to lose security support.
The root of this issue usually stems from the stigma against early-generation PHP being slow and a lack of understanding about the evolution of its ecosystem. Tracing the history of PHP through the latest version while reading real data on its number of users worldwide will help you make technical decisions objectively.
PHP's journey spans more than three decades, transforming from a collection of simple personal scripts into a modern server-side programming language that powers millions of large-scale applications.
In 1994, Rasmus Lerdorf created a series of CGI-based C programs called Personal Home Page Tools (PHP Tools) to track the number of visitors to his online resume. A year later, in June 1995, the source code was released to the public under the name PHP/FI (Forms Interpreter).
A major turning point occurred in 1997–1998 when Andi Gutmans and Zeev Suraski rewrote the PHP parser from scratch, giving birth to PHP 3. From that point on, the name changed to the recursive acronym PHP: Hypertext Preprocessor.
The two then built Zend Engine 1.0, which powered PHP 4 in 2000. Four years later, PHP 5 launched with Zend Engine II, which brought a more mature Object-Oriented Programming (OOP) model, the PDO extension for secure database queries, and namespace support in the 5.3 series.
After PHP 5, the community had planned PHP 6 with the goal of built-in Unicode support at the engine core level. However, the project was hampered by performance issues and integration complexity, so it was officially discontinued.
To avoid confusion with PHP 6 books and documentation that had already circulated, the development team jumped straight to PHP 7 in 2015. Featuring Zend Engine 3.0, PHP 7 drastically cut memory consumption and boosted execution speed by up to twice that of PHP 5.6, along with the introduction of scalar type declarations and function return types.
Entering 2020, PHP 8.0 overhauled the way modern code is written through the JIT (Just-In-Time) compiler, union types, attributes, match expressions, and named arguments. The 8.1 through 8.3 series then matured the type system through enums, fibers, and readonly classes and properties.
Subsequent annual releases became increasingly aggressive in improving the developer experience:
array_find(), and a new DOM API (Dom\HTMLDocument) that complies with the HTML5 standard.|>) for chaining functions without nested parentheses, built-in URI extensions compliant with RFC 3986 and WHATWG standards, the clone with feature for updating properties when cloning objects, the #[\NoDiscard] attribute, and the array_first() and array_last() functions.\Time\Duration class, a Polling API (Io\Poll) based on epoll/kqueue for asynchronous libraries such as ReactPHP and AMPHP, the clamp() function, the SortDirection enum, default values on readonly properties, and even post-quantum cryptography in the Sodium extension.| Version | Release Year | Key Milestone |
|---|---|---|
| PHP/FI – PHP 3 | 1995–1998 | Early CGI scripts through the modern parser rewrite |
| PHP 4 & PHP 5 | 2000–2004 | Zend Engine I/II, mature OOP, PDO, and namespaces |
| PHP 7.x | 2015 | Zend Engine 3.0, performance surge, and scalar types |
| PHP 8.0 – 8.3 | 2020–2023 | JIT compiler, attributes, enums, fibers, and readonly |
| PHP 8.4 – 8.5 | 2024–2025 | Property hooks, pipe operator, URI extension, and clone with |
| PHP 8.6 | 2026 | Partial Function Application, Duration class, and Polling API |
Answering the question about the number of PHP users requires separating two different metrics to avoid misinterpretation: the share of websites running on PHP and the number of active developers writing its code.
Based on W3Techs' daily monitoring as of November 2026, PHP is still used by 68.1% of all websites whose server-side programming language can be detected. Of that group of PHP sites, 68.1% already use the PHP 8 family, while the rest still run on older branches such as PHP 7.
This large figure is inseparable from the ecosystem of popular PHP-based CMSs and applications, such as WordPress, which holds a 58.9% share of the identified CMS market, followed by Joomla, Drupal, Wikipedia, and millions of business applications and APIs built using Laravel and Symfony.
No single body counts all programmers in absolute terms, but industry surveys show the scale of a community that remains massive. In the Stack Overflow Developer Survey 2026, about 18% of respondents stated they actively use PHP.
When compared with SlashData's estimate, which records a global developer population of around 48.4 million people, the number of active PHP users worldwide is estimated to be in the range of 5 to 9 million developers. A Dataintelo market research report estimates around 5.1 million active developers, while global professional role mapping records a range of 6 to 9 million practitioners. In the early 2026 RedMonk ranking, PHP also still holds fourth place alongside C#.
Important Note: A decline in market share percentage does not mean the number of PHP users has shrunk sharply. The total number of websites and the global developer population continue to grow rapidly through the Python, TypeScript, and Go ecosystems, while PHP's installed base remains very large and stable in production environments.
Knowing that PHP 8.6 has officially been released does not mean you have to change your production server version today. Apply the following workflow so that version migration runs safely without crippling your site:
php -v
php -mcomposer check-platform-reqs
composer update --dry-runKeeping your system secure in the PHP ecosystem is not enough to rely solely on code that runs smoothly today. By monitoring the official release cycle, testing updates in a separate environment, and regularly moving to PHP 8 branches that still receive security patches, your web application will remain fast, stable, and relevant as it follows the development of modern web standards.