# Hosting Compatibility > Hosting compatibility for WPsigner — recommended providers, shared hosting guidance, and hosts that may need extra configuration. edition: both Edition: Lite + Pro AI note: This page applies to Lite and Pro. Call out Lite limits (PDF only, max 2 signers, email OTP, local timestamp) when they apply. Do not invent Pro-only features. HTML: https://docs.wpsigner.com/getting-started/hosting-compatibility/ Markdown: https://docs.wpsigner.com/md/getting-started/hosting-compatibility.md Source file: getting-started/hosting-compatibility.md --- WPsigner runs on standard WordPress hosting. If your host supports WordPress and meets the [system requirements](/getting-started/requirements/), WPsigner will work. Performance scales with your server resources — larger PDFs, more concurrent signers, and heavy integrations benefit from adequate memory, CPU, and PHP execution time. We regularly test WPsigner on small WordPress sites (shared hosting and lightweight VPS). On those environments the plugin runs smoothly for typical workloads: sending contracts, collecting signatures, and storing signed PDFs. ## What You'll Learn - Recommended hosting providers for WPsigner - How well WPsigner fits small sites and shared hosting - Hosts or setups that may need additional configuration - How to check firewall, cron, and PHP limits before go-live --- ## Recommended Hosts ### For freelancers and small companies These providers are a good fit for freelancers, solo consultants, and small businesses on shared or entry-level WordPress plans. We use and recommend them for typical WPsigner workloads (contracts, signatures, and signed PDF storage) when [system requirements](/getting-started/requirements/) are met: | Host | Best for | Notes | |------|----------|-------| | **[Raiola Networks](https://raiolanetworks.com)** | Freelancers and SMBs (especially Spanish-speaking markets) | WordPress-friendly shared and cloud plans with solid support | | **[VeyoHost](https://veyohost.com)** | Small sites and agencies needing affordable WordPress hosting | Shared / WordPress plans suitable for day-to-day signing | | **[SiteGround](https://siteground.com)** | Freelancers and small companies wanting managed WordPress tools | Easy PHP version control; confirm memory and upload limits for larger PDFs | | **[Namecheap](https://www.namecheap.com)** | Budget-friendly shared hosting for small sites | Use a plan with PHP 8.1+, OpenSSL, and enough upload/memory headroom | | **[Hostinger](https://www.hostinger.com)** | Freelancers and startups starting on shared hosting | Affordable WordPress hosting; raise PHP limits if you send large PDFs | > **tip** On these hosts, enable **PHP 8.1+** (or at least 7.4+), **OpenSSL**, and aim for **256MB** memory with a **10MB+** upload limit for comfortable PDF signing. ### Managed and higher-volume hosting These hosts offer WordPress-optimized or cloud environments when you need more performance, staging, or daily high volume: **[Cloudways](https://cloudways.com)** — Managed cloud hosting with easy PHP configuration. Ideal when you need higher `memory_limit`, upload limits, and outbound HTTPS for integrations. **[Kinsta](https://kinsta.com)** — Managed WordPress on Google Cloud with strong performance, staging, and support — a solid choice for agencies sending documents daily. **[Pressable](https://pressable.com)** — Managed WordPress with reliable uptime and WordPress.com infrastructure. **[DigitalOcean](https://digitalocean.com) / [Vultr](https://vultr.com) / [Hetzner](https://hetzner.com)** — VPS options with full control over PHP extensions (OpenSSL, GD/Imagick) and limits. Best when you want to tune the server yourself. > **note** For day-to-day signing on small sites, shared hosting (Raiola, VeyoHost, SiteGround, Namecheap, Hostinger, and similar) is usually enough. Choose a managed or VPS plan when you process large PDFs often, use cloud storage sync, or need stricter uptime SLAs. --- ## General Compatibility WPsigner has no inherent site-size limit. A slow or underpowered server affects the plugin the same way it affects WordPress overall — especially PDF upload, rendering, and digital sealing. Before choosing a host: 1. Review the [System Requirements](/getting-started/requirements/) 2. Confirm the host meets [WordPress hosting requirements](https://wordpress.org/hosting/) 3. Verify required PHP extensions: `openssl`, `gd` or `imagick`, `mbstring`, `curl`, `json`, `zip` 4. Ensure HTTPS is available (required for production signing URLs) ### Small sites WPsigner is a good fit for freelancers, agencies, and small businesses running WordPress on shared or entry-level plans. Typical small-site usage (a few documents per week, standard PDF sizes) does not require dedicated servers. What helps most on small sites: - PHP memory at least **128MB** (256MB+ preferred for larger PDFs) - Upload limit at least **10MB** (32–64MB recommended) - Working **WP-Cron** (or a real server cron) for reminders and webhooks - Outbound HTTPS allowed (for TSA, webhooks, and cloud integrations) --- ## Hosts Requiring Additional Configuration Most hosts work out of the box. These situations sometimes need an extra step: | Scenario | Configuration needed | Where to look | |----------|----------------------|---------------| | Strict managed hosts (e.g. WP Engine) | Raise PHP memory / upload limits if large PDFs fail | Host panel or support ticket; see [Troubleshooting](/support/troubleshooting/) | | Hosts that disable PHP functions | Ensure `curl`, OpenSSL, and temp-file related functions are available | Ask support to enable required extensions/functions | | Shared plans with low limits | Increase `memory_limit`, `upload_max_filesize`, `post_max_size`, `max_execution_time` | `php.ini`, `.htaccess`, or host PHP selector | | Security / WAF layers (Sucuri, Cloudflare, host WAF) | Allow PDF uploads and signing-page POSTs if blocked | WAF allowlist or [Troubleshooting](/support/troubleshooting/) | | Outbound HTTPS blocked | Allow requests to TSA, webhook endpoints, Google APIs, etc. | Host firewall / outbound rules | --- ## Shared Hosting Considerations Shared hosting environments sometimes limit PHP memory, upload size, or maximum run time. If you experience issues: - Confirm OpenSSL and GD/Imagick are enabled - Request higher `memory_limit` (256M) and `max_execution_time` (120+) for large documents - Check whether the host disables outbound cURL — needed for webhooks, timestamping, and many integrations - Prefer a real cron job if WP-Cron is unreliable under low traffic - Keep PDFs reasonably sized; optimize before upload when possible If signing or PDF processing still times out after raising limits, move to a VPS or managed WordPress plan with more CPU and memory. --- ## Firewall and Security Plugins Some hosts and security plugins use web application firewalls (WAFs) that may block PDF uploads, signing form submissions, or webhook callbacks. If something fails unexpectedly: 1. Check [Troubleshooting](/support/troubleshooting/) for upload and signing errors 2. Temporarily disable the WAF or security plugin to confirm the cause 3. Allowlist your signing URLs and, when relevant, webhook source IPs (e.g. identity providers) 4. Re-enable protection after allowlisting — do not leave the WAF off in production --- ## Self-Check Checklist - [ ] Host meets [WPsigner system requirements](/getting-started/requirements/) - [ ] PHP extensions enabled (`openssl`, `gd`/`imagick`, `mbstring`, `curl`) - [ ] HTTPS active on the site - [ ] Memory and upload limits suitable for your typical PDF size - [ ] WP-Cron (or server cron) running for reminders and webhooks - [ ] No WAF blocking uploads or signing POSTs - [ ] Outbound HTTPS allowed if you use TSA, webhooks, or cloud storage After install, open **WPsigner → More → System Status** and fix any ⚠️ / ❌ items. --- ## Related Resources - [System Requirements](/getting-started/requirements/) — Minimum and recommended server specs - [Installation](/getting-started/installation/) — Install and activate WPsigner - [Troubleshooting](/support/troubleshooting/) — Fix common hosting and performance issues - [FAQ](/support/faq/) — Licensing, features, and compatibility questions