ParadigmImperative, functional, object-oriented, procedural, reflective
Designed byRasmus Lerdorf
DeveloperThe PHP Development Team, Zend Technologies
First appeared1995; 24 years ago (1995)[1]
Stable release
7.3.11[2] / October 24, 2019; 21 days ago (2019-10-24)
Preview release
7.4.0 RC5[3] / October 31, 2019; 14 days ago (2019-10-31)
Typing disciplineDynamic, weak

since version 7.0:

Implementation languageC (primarily; some components C++)
OSUnix-like, Windows
LicensePHP License (most of Zend engine under Zend Engine License)
Major implementations
Zend Engine, HHVM, Phalanger, Quercus, Parrot
Influenced by
Perl, C, C++, Java, Tcl,[1] JavaScript, Hack[5]

PHP: Hypertext Preprocessor (or simply PHP) is a general-purpose programming language originally designed for web development. It was originally created by Rasmus Lerdorf in 1994;[6] the PHP reference implementation is now produced by The PHP Group.[7] PHP originally stood for Personal Home Page,[6] but it now stands for the recursive initialism PHP: Hypertext Preprocessor.[8]

PHP code may be executed with a command line interface (CLI), embedded into HTML code, or used in combination with various web template systems, web content management systems, and web frameworks. PHP code is usually processed by a PHP interpreter implemented as a module in a web server or as a Common Gateway Interface (CGI) executable. The web server outputs the results of the interpreted and executed PHP code, which may be any type of data, such as generated HTML code or binary image data. PHP can be used for many programming tasks outside of the web context, such as standalone graphical applications[9] and robotic drone control.[10]

The standard PHP interpreter, powered by the Zend Engine, is free software released under the PHP License. PHP has been widely ported and can be deployed on most web servers on almost every operating system and platform, free of charge.[11]

The PHP language evolved without a written formal specification or standard until 2014, with the original implementation acting as the de facto standard which other implementations aimed to follow. Since 2014, work has gone on to create a formal PHP specification.[12]

As of September 2019, over 60% of sites on the web using PHP are still on discontinued/"EOLed"[13] version 5.6 or older;[14] versions prior to 7.1 are no longer officially supported by The PHP Development Team,[15] but security support is provided by third parties, such as Debian.[16]


Early history

Rasmus Lerdorf, who wrote the original Common Gateway Interface (CGI) component, together with Andi Gutmans and Zeev Suraski, who rewrote the parser that formed PHP 3.

PHP development began in 1994 when Rasmus Lerdorf wrote several Common Gateway Interface (CGI) programs in C,[17][18][19] which he used to maintain his personal homepage. He extended them to work with web forms and to communicate with databases, and called this implementation "Personal Home Page/Forms Interpreter" or PHP/FI.

PHP/FI could be used to build simple, dynamic web applications. To accelerate bug reporting and improve the code, Lerdorf initially announced the release of PHP/FI as "Personal Home Page Tools (PHP Tools) version 1.0" on the Usenet discussion group comp.infosystems.www.authoring.cgi on June 8, 1995.[20][21] This release already had the basic functionality that PHP has today. This included Perl-like variables, form handling, and the ability to embed HTML. The syntax resembled that of Perl, but was simpler, more limited and less consistent.[7]

An example of the early PHP syntax:

<!--include /text/header.html-->

<!--getenv HTTP_USER_AGENT-->
<!--ifsubstr $exec_result Mozilla-->
  Hey, you are using Netscape!<p>

<!--sql database select * from table where user='$username'-->
<!--ifless $numentries 1-->
  Sorry, that record does not exist<p>
<!--endif exit-->
  Welcome <!--$user-->!<p>
  You have <!--$index:0--> credits left in your account.<p>

<!--include /text/footer.html-->

Early PHP was not intended to be a new programming language, and grew organically, with Lerdorf noting in retrospect: "I don't know how to stop it, there was never any intent to write a programming language [...] I have absolutely no idea how to write a programming language, I just kept adding the next logical step on the way."[22] A development team began to form and, after months of work and beta testing, officially released PHP/FI 2 in November 1997.

The fact that PHP was not originally designed, but instead was developed organically has led to inconsistent naming of functions and inconsistent ordering of their parameters.[23] In some cases, the function names were chosen to match the lower-level libraries which PHP was "wrapping",[24] while in some very early versions of PHP the length of the function names was used internally as a hash function, so names were chosen to improve the distribution of hash values.[25]

PHP 3 and 4

This is an example of custom PHP code for the WordPress content management system.

Zeev Suraski and Andi Gutmans rewrote the parser in 1997 and formed the base of PHP 3, changing the language's name to the recursive acronym PHP: Hypertext Preprocessor.[7][26] Afterwards, public testing of PHP 3 began, and the official launch came in June 1998. Suraski and Gutmans then started a new rewrite of PHP's core, producing the Zend Engine in 1999.[27] They also founded Zend Technologies in Ramat Gan, Israel.[7]

On May 22, 2000, PHP 4, powered by the Zend Engine 1.0, was released.[7] As of August 2008 this branch reached version 4.4.9. PHP 4 is no longer under development nor will any security updates be released.[28][29]


On July 14, 2004, PHP 5 was released, powered by the new Zend Engine II.[7] PHP 5 included new features such as improved support for object-oriented programming, the PHP Data Objects (PDO) extension (which defines a lightweight and consistent interface for accessing databases), and numerous performance enhancements.[30] In 2008, PHP 5 became the only stable version under development. Late static binding had been missing from PHP and was added in version 5.3.[31][32]

Many high-profile open-source projects ceased to support PHP 4 in new code as of February 5, 2008, because of the GoPHP5 initiative,[33] provided by a consortium of PHP developers promoting the transition from PHP 4 to PHP 5.[34][35]

Over time, PHP interpreters became available on most existing 32-bit and 64-bit operating systems, either by building them from the PHP source code, or by using pre-built binaries.[36] For PHP versions 5.3 and 5.4, the only available Microsoft Windows binary distributions were 32-bit IA-32 builds,[37][38] requiring Windows 32-bit compatibility mode while using Internet Information Services (IIS) on a 64-bit Windows platform. PHP version 5.5 made the 64-bit x86-64 builds available for Microsoft Windows.[39]

Official security support for PHP 5.6 ended on 31 December 2018,[40] but Debian 8.0 Jessie will extend support until June 2020.[16]

PHP 6 and Unicode

PHP received mixed reviews due to lacking native Unicode support at the core language level.[41][42] In 2005, a project headed by Andrei Zmievski was initiated to bring native Unicode support throughout PHP, by embedding the International Components for Unicode (ICU) library, and representing text strings as UTF-16 internally.[43] Since this would cause major changes both to the internals of the language and to user code, it was planned to release this as version 6.0 of the language, along with other major features then in development.[44]

However, a shortage of developers who understood the necessary changes, and performance problems arising from conversion to and from UTF-16, which is rarely used in a web context, led to delays in the project.[45] As a result, a PHP 5.3 release was created in 2009, with many non-Unicode features back-ported from PHP 6, notably namespaces. In March 2010, the project in its current form was officially abandoned, and a PHP 5.4 release was prepared containing most remaining non-Unicode features from PHP 6, such as traits and closure re-binding.[46] Initial hopes were that a new plan would be formed for Unicode integration, but as of 2014 none had been adopted.


During 2014 and 2015, a new major PHP version was developed, which was numbered PHP 7. The numbering of this version involved some debate.[47] While the PHP 6 Unicode experiment had never been released, several articles and book titles referenced the PHP 6 name, which might have caused confusion if a new release were to reuse the name.[48] After a vote, the name PHP 7 was chosen.[49]

The foundation of PHP 7 is a PHP branch that was originally dubbed PHP next generation (phpng). It was authored by Dmitry Stogov, Xinchen Hui and Nikita Popov,[50] and aimed to optimize PHP performance by refactoring the Zend Engine while retaining near-complete language compatibility.[51] As of 14 July 2014, WordPress-based benchmarks, which served as the main benchmark suite for the phpng project, showed an almost 100% increase in performance. Changes from phpng are also expected to make it easier to improve performance in the future, as more compact data structures and other changes are seen as better suited for a successful migration to a just-in-time (JIT) compiler.[52] Because of the significant changes, the reworked Zend Engine is called Zend Engine 3, succeeding Zend Engine 2 used in PHP 5.[53]

Because of major internal changes in phpng it must receive a new major version number of PHP, rather than a minor PHP 5 release, according to PHP's release process.[54] Major versions of PHP are allowed to break backward-compatibility of code and therefore PHP 7 presented an opportunity for other improvements beyond phpng that require backward-compatibility breaks. In particular, it involved the following changes:

  • Many fatal- or recoverable-level legacy PHP error mechanisms were replaced with modern object-oriented exceptions[55]
  • The syntax for variable dereferencing was reworked to be internally more consistent and complete, allowing the use of the operators ->, [], (),{}, and ::, with arbitrary meaningful left-side expressions[56]
  • Support for legacy PHP 4-style constructor methods was deprecated[57]
  • The behavior of the foreach statement was changed to be more predictable[58]
  • Constructors for the few classes built-in to PHP which returned null upon failure were changed to throw an exception instead, for consistency[59]
  • Several unmaintained or deprecated server application programming interfaces (SAPIs) and extensions were removed from the PHP core, most notably the legacy mysql extension[60]
  • The behavior of the list() operator was changed to remove support for strings[61]
  • Support was removed for legacy ASP-style delimiters <% and %> and <script language="php"> ... </script>[62]
  • An oversight allowing a switch statement to have multiple default clauses was fixed[63]
  • Support for hexadecimal number support in some implicit conversions from strings to number types was removed[64]
  • The left-shift and right-shift operators were changed to behave more consistently across platforms[65]
  • Conversions between integers and floating point numbers were tightened and implemented more consistently across platforms[65][66]

PHP 7 also included new language features. Most notably, it introduces return type declarations for functions[67] which complement the existing parameter type declarations, and support for the scalar types (integer, float, string, and boolean) in parameter and return type declarations.[68]

Release history

Version Release date Supported until[15] Notes
Old version, no longer supported: 1.0 8 June 1995 Officially called "Personal Home Page Tools (PHP Tools)". This is the first use of the name "PHP".[7]
Old version, no longer supported: 2.0 1 November 1997 Officially called "PHP/FI 2.0". This is the first release that could actually be characterised as PHP, being a standalone language with many features that have endured to the present day.
Old version, no longer supported: 3.0 6 June 1998 20 October 2000[15] Development moves from one person to multiple developers. Zeev Suraski and Andi Gutmans rewrite the base for this version.[7]
Old version, no longer supported: 4.0 22 May 2000 23 June 2001[15] Added more advanced two-stage parse/execute tag-parsing system called the Zend engine.[69]
Old version, no longer supported: 4.1 10 December 2001 12 March 2002[15] Introduced "superglobals" ($_GET, $_POST, $_SESSION, etc.)[69]
Old version, no longer supported: 4.2 22 April 2002 6 September 2002[15] Disabled register_globals by default. Data received over the network is not inserted directly into the global namespace anymore, closing possible security holes in applications.[69]
Old version, no longer supported: 4.3 27 December 2002 31 March 2005[15] Introduced the command-line interface (CLI), to supplement the CGI.[69][70]
Old version, no longer supported: 4.4 11 July 2005 7 August 2008[15] Fixed a memory corruption bug, which required breaking binary compatibility with extensions compiled against PHP version 4.3.x.[71]
Old version, no longer supported: 5.0 13 July 2004 5 September 2005[15] Zend Engine II with a new object model.[72]
Old version, no longer supported: 5.1 24 November 2005 24 August 2006[15] Performance improvements with introduction of compiler variables in re-engineered PHP Engine.[72] Added PHP Data Objects (PDO) as a consistent interface for accessing databases.[73]
Old version, no longer supported: 5.2 2 November 2006 6 January 2011[15] Enabled the filter extension by default. Native JSON support.[72]
Old version, no longer supported: 5.3 30 June 2009 14 August 2014[15] Namespace support; late static bindings, jump label (limited goto), closures, PHP archives (phar), garbage collection for circular references, improved Windows support, sqlite3, mysqlnd as a replacement for libmysql as underlying library for the extensions that work with MySQL, fileinfo as a replacement for mime_magic for better MIME support, the Internationalization extension, and deprecation of ereg extension.
Old version, no longer supported: 5.4 1 March 2012 3 September 2015[15] Trait support, short array syntax support. Removed items: register_globals, safe_mode, allow_call_time_pass_reference, session_register(), session_unregister() and session_is_registered(). Built-in web server.[74] Several improvements to existing features, performance and reduced memory requirements.
Old version, no longer supported: 5.5 20 June 2013 10 July 2016[75] Support for generators, finally blocks for exceptions handling, OpCache (based on Zend Optimizer+) bundled in official distribution.[76]
Old version, no longer supported: 5.6 28 August 2014 31 December 2018[75] Constant scalar expressions, variadic functions, argument unpacking, new exponentiation operator, extensions of the use statement for functions and constants, new phpdbg debugger as a SAPI module, and other smaller improvements.[77]
6.x Not released N/A Abandoned version of PHP that planned to include native Unicode support.[78][79]
Old version, no longer supported: 7.0 3 December 2015[80] 3 December 2018[54] Zend Engine 3 (performance improvements[52] and 64-bit integer support on Windows[81]), uniform variable syntax,[56] AST-based compilation process,[82] added Closure::call(),[83] bitwise shift consistency across platforms,[84] ?? (null coalesce) operator,[85] Unicode code point escape syntax,[86] return type declarations,[67] scalar type (integer, float, string and boolean) declarations,[68] <=> "spaceship" three-way comparison operator,[87] generator delegation,[88] anonymous classes,[89] simpler and more consistently available CSPRNG API,[90] replacement of many remaining internal PHP "errors" with the more modern exceptions,[55] and shorthand syntax for importing multiple items from a namespace.[91]
Older version, yet still supported: 7.1 1 December 2016 1 December 2019[75] void return type,[92] class constant visibility modifiers[93]
Older version, yet still supported: 7.2 30 November 2017 30 November 2020[75] Object parameter and return type hint,[94] Libsodium extension,[95] Abstract method overriding,[96] Parameter type widening[97]
Current stable version: 7.3 6 December 2018[98] 6 December 2021 Flexible Heredoc and Nowdoc syntax,[99] support for reference assignment and array deconstruction with list(),[100] PCRE2 support,[101] hrtime() function[102]
Future release: 7.4 28 November 2019[103] December 2022 Typed Properties 2.0,[104] Preloading,[105] Null Coalescing Assignment Operator,[106] Improve openssl_random_pseudo_bytes,[107] Weak References,[108] FFI – Foreign Function Interface[109]

Always available hash extension,[110] Password Hash Registry,[111] Split multibyte string,[112] Reflection for references,[113] Unbundle ext/wddx,[114] New custom object serialization mechanism[115]

Future release: 8.0 Q4 2020 or Q1 2021 Q4 2023 or Q1 2024 Just In Time compilation (JIT),[116] arrays starting with a negative index,[117] consistent type errors for internal functions,[118] fatal error for incompatible method signatures[119]
Old version
Older version, still supported
Latest version
Latest preview version
Future release

Beginning on June 28, 2011, the PHP Development Team implemented a timeline for the release of new versions of PHP.[54] Under this system, at least one release should occur every month. Once per year, a minor release should occur which may include new features. Every minor release should at least be supported for two years with security and bug fixes, followed by at least one year of only security fixes, for a total of a three-year release process for every minor release. No new features, unless small and self-contained, are to be introduced into a minor release during the three-year release process.