Skip to main content
The Extensions tab shows every PHP extension available for the active version, as a long checkbox list. Tick a box to load the extension on the next PHP request; untick to unload.
Extensions tab with the full extension list

Common extensions, what they’re for

ExtensionUsed by
mysqli / pdo_mysqlAny MySQL connection from PHP. WordPress, Laravel, anything.
gdImage manipulation. WordPress media uploads, thumbnail generation.
imagickHigher-quality image manipulation than gd. Some plugins prefer it.
intlInternationalization functions. Composer packages frequently require it.
mbstringMultibyte string handling. Required by most modern PHP frameworks.
xml, dom, simplexmlXML parsing. Often required by Composer itself, plus any RSS/SOAP code.
curlOutbound HTTP from PHP. Required by anything fetching APIs.
zipZIP archive support. WordPress plugin/theme installs use it.
bcmath / gmpArbitrary precision math. Crypto, finance, some Magento components.
redisRedis client. Object cache plugins, queue workers.
opcachePHP bytecode cache. Always on. Don’t turn it off.
soapSOAP/WSDL clients. A handful of payment gateways still need it.
ldapLDAP authentication. Rare on shared hosting.

Apply changes

After ticking or unticking, click Save. The next PHP request loads the new extension list. There’s no service restart needed.
If you’re unsure whether a plugin needs an extension, check its requirements page. Most plugins list “PHP 8.0+ with mbstring, intl, gd”. Match the list and move on.

How this differs from pecl install

The selector loads extensions that are pre-built for each PHP version. PECL lets you compile arbitrary extensions from source. The selector is faster, safer, and the right tool for 99% of cases. PECL only matters when:
  • You need a specific patched build that the cPanel selector doesn’t expose.
  • You’re testing a beta extension (e.g., apcu betas, custom builds of imagick).
For PECL workflows you need SSH and a writable build environment. We can’t always grant the build privileges on shared plans. Check with support first.

Common issues

Either it’s not packaged for our PHP build (rare for mainstream extensions; common for experimental ones), or it’s been deprecated. The most common surprise: mcrypt was removed from PHP 7.2 onwards and is no longer in the list. Switch to openssl or sodium for modern crypto.
Likely you ticked the box but didn’t click Save. The page accepts ticks without saving until you hit the button. Reload the page to confirm; ticked-and-saved extensions stay ticked across reloads.
Some extensions are mutually exclusive. The selector usually warns when you try to enable a conflicting pair. If your PHP suddenly errors on a function from one of them, untick the other.
Persistent processes like long-lived queue workers don’t pick up extension changes until they restart. The HTTP-handler PHP picks up changes on the next request; CLI cron jobs pick up changes on the next invocation. If you have a daemon, you need to restart it.

Need a hand?