Are any WordPress plugins or themes banned at SwiftPress?
How we approach plugin and theme compatibility, what we may ask you to change, and why nulled software is never allowed.
In general: The vast majority of WordPress plugins and themes work fine on SwiftPress. We don’t publish a long “banned list” because compatibility depends on your stack, traffic, and configuration—but we do reserve the right to disable or ask you to remove anything that harms security, stability, or other customers on the platform.
Below is how we think about it, and what we never allow.
Most plugins and themes are fine
If it’s actively maintained and widely used, it will usually run on SwiftPress like anywhere else. Results still vary by site: the same caching or minification plugin can be perfect on one store and problematic on another because of theme or plugin interactions.
We strongly recommend testing after adding or updating plugins—especially performance, security, and backup tools—and rolling out changes in staging when you have it.
What we may ask you to disable or remove
We don’t remove software without cause. If something is found to hurt performance, break caching or TLS, hammer disk or CPU, or weaken isolation for your neighbours, we may disable it to protect the platform and contact you to adjust or remove it permanently.
Examples of types of extensions that sometimes cause issues on managed WordPress hosts (not an exhaustive ban list):
- Duplicate or conflicting “full stack” cache / CDN plugins that fight your host’s edge and server caching, causing broken pages or stale content.
- Aggressive file-integrity or change monitors that scan constantly and overload I/O on busy sites.
- Image or CDN plugins that bypass or duplicate what the platform already does in a way that breaks delivery or caching—configuration matters more than the name on the tin.
- Plugins known by their authors to be incompatible with a given hosting architecture (always check the plugin’s documentation).
If you’re unsure, ask us before you rely on a niche tool for something core—we can usually suggest a safer pattern for SwiftPress.
Plugins from other hosting companies
Many hosts (e.g. HostGator, Bluehost, Kinsta, WP Engine, etc.) offer their own WordPress plugins or must-use packages tuned only for their environment.
If you migrate a site to SwiftPress, remove or replace those host-specific plugins. They often:
- Expect APIs or paths that don’t exist here
- Clash with our caching, CDN, or security stack
- Add overhead without benefit
We focus on standards-based WordPress—your site should not depend on another provider’s proprietary plugin to function.
Nulled, pirated, or unofficial “premium” copies
Nulled or cracked plugins and themes—sometimes labelled “free” or “GPL” on shady sites—are forbidden on SwiftPress.
They are unlicensed copies of paid software. They are often bundled with backdoors, malware, or phone-home code that abuse your site, visitors, or server resources. Using them puts you, your customers, and our infrastructure at risk.
Only install plugins and themes from:
- WordPress.org (free, reviewed)
- The original author’s official site or authorised resellers
- Legitimate marketplaces with verifiable licensing
If you’re not sure a download is legitimate, don’t install it.
Summary
| Topic | SwiftPress stance |
|---|---|
| Most plugins/themes | Allowed when they behave responsibly. |
| Problematic extensions | May be disabled if they harm the platform; we’ll work with you on alternatives. |
| Other hosts’ plugins | Remove after migration when they’re not needed. |
| Nulled / pirated software | Forbidden. |
Need help?
Use — same as the Support link in the site footer (opens the chat widget). You can also sign in at my.swiftpress.io. We don’t offer email support — see How to contact customer support. If something in this article doesn’t match your dashboard, and we’ll point you to the right screen.