Contents
MailWizz and phpList both run on PHP/MySQL infrastructure but represent different paths within the self-hosted PHP email marketing category. MailWizz is a commercial application built on modern Yii framework with $86 one-time license, providing polished UI, drag-and-drop editor, native multi-tenant architecture, and plugin marketplace. phpList is a free AGPLv3 open-source platform with longer history, trusted by 75,000+ organisations across 35 countries, focused on deliverability at massive scale, with functional but dated UI. The 2026 decision typically reduces to operator priorities: MailWizz suits operators wanting modern UI and multi-tenant capability willing to pay license cost; phpList suits operators preferring free software and proven deliverability heritage willing to accept UI tradeoffs. The phpList Hosted option starting at $1/month provides additional path for operators wanting managed open-source.
This comparison covers the practical decision between MailWizz and phpList in 2026: both platforms' shared PHP/MySQL technology foundation, MailWizz's commercial modern approach with comprehensive features, phpList's open-source heritage with massive established deployment base, the phpList Hosted managed option providing managed open source at low cost, feature comparison covering UI quality, drag-and-drop editing, multi-tenant capability, automation depth, the CMS integration advantage phpList provides through native plugins, cost comparison including phpList's free software versus MailWizz's small license cost, operator profile fit, and the decision framework for operators choosing between two viable PHP-based self-hosted approaches.
Two PHP paths in self-hosted email
One emerged commercial. The other emerged free.
MailWizz and phpList both occupy the self-hosted PHP email marketing category but reached it through different paths reflecting different software development philosophies and timing.
phpList emerged in the early 2000s as one of the first open-source PHP applications focused on bulk email marketing. The project predates much of modern web development infrastructure; it has evolved through PHP version transitions, hosting environment changes, and feature expansion over more than two decades. The longevity produces both advantages (proven reliability, established deployment patterns, deep community) and disadvantages (UI that shows age, architectural decisions made for older PHP versions, accumulated technical debt).
MailWizz emerged in 2013 as commercial competition to phpList and similar open-source alternatives. The newer project benefited from modern PHP framework patterns (Yii framework), cleaner UI design influenced by modern web applications, commercial development discipline producing more polished user experience. The commercial model funds continuous development and support unavailable to volunteer-driven open source.
The path differences produce ongoing implications:
UI design era. MailWizz UI reflects post-2013 web design with modern patterns; phpList UI reflects earlier eras despite ongoing updates, producing functional but visually dated interface.
Architecture decisions. MailWizz built on Yii framework with established patterns; phpList uses custom architecture accumulated over decades with some legacy components.
Feature priorities. MailWizz adds features matching commercial competitive pressures; phpList adds features matching community contributions and user demand.
Documentation style. MailWizz documentation oriented toward modern web operators; phpList documentation extensive but reflects different documentation eras.
Support model. MailWizz provides commercial support with response time expectations; phpList offers community forums plus paid hosted support tiers.
Update mechanism. Both update through standard PHP application patterns; MailWizz commercial releases follow product roadmap; phpList community releases follow contributor schedule.
Neither path is objectively superior; the choice depends on operator priorities. Operators wanting polished UI and commercial discipline favour MailWizz; operators wanting free software and proven heritage favour phpList.
MailWizz overview
MailWizz's commercial PHP approach has specific characteristics.
Yii framework foundation. Built on Yii 2.x providing mature PHP MVC framework. Modular component architecture; established security patterns; extensive plugin ecosystem.
Commercial perpetual licensing. $86 one-time for Standard License; $275 Extended License for SaaS commercial offering. Lifetime updates included.
Modern UI design. Polished admin interface with intuitive navigation; responsive design works on mobile and desktop; visual builder for campaigns; modern web application patterns throughout.
Drag-and-drop email editor. Native visual builder for campaign creation; HTML editor for advanced users; plain text editor for simple campaigns; comprehensive template library.
Multi-tenant native architecture. Customer accounts built-in for agencies and platform operators. Each customer has isolated lists, campaigns, statistics. Platform operator administers overall installation.
BYOSP delivery. Supports Amazon SES, SendGrid, Mailgun, SparkPost, generic SMTP through configurable delivery servers. Multiple delivery servers with rotation logic.
A/B testing native. Subject line and content variation testing with automatic winner selection.
Plugin marketplace. Third-party plugin marketplace extending functionality. Operators can develop custom plugins.
Comprehensive Web API. Full REST API for programmatic operations. Webhook system. PHP hooks for customisation.
Documentation and support. Modern documentation; email support included with license; community forum; paid premium support tiers available.
Active commercial development. Regular feature updates; security patches; modern PHP version support; product roadmap published.
Typical MailWizz deployment costs:
- LAMP stack VPS: $10-200/month
- MailWizz license: $86 one-time
- SMTP service: $0-50+/month
- Domain + SSL: ~$15/year
- Total monthly: $20-300+ depending on infrastructure
phpList overview
phpList's open-source PHP approach has different characteristics.
AGPLv3 open-source license. Free software; source code available on GitHub (phpList/phplist3 repository); commercial use permitted. Self-hosted free; modifications must be open-sourced under AGPLv3 if used to provide network service.
Long deployment history. 25+ year project; trusted by 75,000+ organisations across 35 countries; available in 20 languages; estimated 25+ billion campaign messages sent through phpList installations (2018 statistic, likely much higher now).
Established deliverability focus. phpList's design prioritises deliverability at massive scale. Features include message-queue management with load balancing and throttling; automatic throttle calibration; intelligent bounce processing with regex-based handling; continuous blacklist monitoring; automatic spam complaint processing from major mail hosts.
Plugin-based architecture. Extensible through plugins; plugins maintained by phpList project and community; integration plugins for major CMS platforms.
Custom PHP architecture. phpList uses custom PHP architecture rather than modern framework; the codebase reflects evolution from older PHP versions; functional but architecturally less modern than MailWizz's Yii framework.
Functional UI. Trevelin theme provides functional admin interface; UI is utilitarian rather than polished; campaign workflows clear but visually dated compared to modern alternatives.
Subscription forms and integration. Built-in subscription forms; CSV import with attribute mapping; foreign key support for synchronisation with external databases; CMS plugin integrations (WordPress, WooCommerce, Drupal, Joomla, etc.).
RSS feed integration. phpList can read RSS sources and send contents on regular basis; users choose feed frequency. Useful for content publishers wanting newsletter automation from blog feeds.
Multilingual support. Available in 20 languages; translation contributions through translate.phplist.org community.
Documentation and community. Extensive documentation under Creative Commons license; user forums; IRC chat for real-time community help; documentation organised for different skill levels (beginners, regular users, power users, developers).
Active open-source development. Continued releases through phplist3 repository; community contributions; commercial sponsor (phpList Ltd) provides funded development plus paid hosted service.
Typical phpList self-hosted costs:
- LAMP stack VPS: $10-200/month
- phpList software: $0 (AGPLv3 free)
- SMTP service: $0-50+/month
- Domain + SSL: ~$15/year
- Total monthly: $15-250+ depending on infrastructure
phpList Hosted alternative
phpList offers managed hosting as commercial product, providing alternative path between fully self-hosted and SaaS alternatives.
phpList Hosted characteristics:
- Managed by phpList Ltd. The commercial entity behind phpList project provides managed hosting using same open-source software operators could self-host.
- Free trial forever. 300 messages monthly free; suitable for testing and very low volume operations.
- Basic plans from $1/month. Low entry pricing for managed hosting; specifics depend on subscriber and message volume.
- Tailored pricing. Higher-volume plans use custom pricing based on requirements; phpList sales team configures plans.
- Specialist support included. Expert email marketing support from phpList team; testimonials emphasise quality of support including unblocking IPs and deliverability consultation.
- Same software, managed infrastructure. Operators get phpList open-source software running on phpList's managed infrastructure; data ownership preserved; migration to self-hosted possible.
- Technical configuration managed. Authentication (SPF, DKIM, DMARC), deliverability infrastructure, server maintenance handled by phpList Hosted team.
The phpList Hosted option creates interesting comparison dynamics:
For very low volume operators: phpList Hosted at $1/month basic is cheaper than MailWizz self-hosted (which requires hosting infrastructure even at low volume). Free trial provides indefinite low-volume capability.
For moderate-volume operators: phpList Hosted costs likely exceed MailWizz self-hosted total cost at typical operational scales. The managed convenience trades against MailWizz's one-time license amortising over years.
For high-volume operators: phpList Hosted custom pricing approaches commercial managed alternatives; self-hosted MailWizz or phpList becomes more economical.
For operators wanting to migrate between hosted and self-hosted: phpList enables data migration between phpList Hosted and self-hosted installations. The flexibility provides operational option not available with MailWizz which is self-hosted only.
The phpList Hosted option means the MailWizz vs phpList comparison has three configurations: MailWizz self-hosted, phpList self-hosted, and phpList Hosted managed. Each fits different operational profiles.
Feature comparison
Feature comparison between MailWizz and phpList:
| Feature category | MailWizz | phpList |
|---|---|---|
| License | Commercial $86 perpetual | AGPLv3 free (or phpList Hosted from $1/month) |
| Technology | PHP/MySQL (Yii framework) | PHP/MySQL (custom architecture) |
| Established users | Tens of thousands | 75,000+ organisations across 35 countries |
| UI modernity | Modern responsive design | Functional but dated |
| Drag-and-drop editor | Native | Not native; HTML editing primarily |
| Template library | Templates included | Trevelin theme; community templates |
| Multi-tenant accounts | Native customer accounts | Not native; single installation |
| SMTP providers | Multiple (BYOSP) | Standard SMTP; multi-server queues |
| A/B testing | Native subject/content | Limited; community plugins |
| Segmentation | Rule-based custom fields | Unlimited list segmentation with attributes |
| Automation | Autoresponders, time-based, rule engine | Drip campaigns, RSS feeds, basic automation |
| RSS-to-email | Plugin available | Native RSS feed reading |
| Plugin architecture | Native marketplace | Plugin system; community plugins |
| API | Comprehensive REST API | Multiple APIs available |
| Webhooks | Full webhook support | Webhook support |
| Bounce handling | Configurable bounce servers | Intelligent bounce processing policy-based |
| CMS integrations | Custom via API | Native: WordPress, WooCommerce, Drupal, Joomla, Magento, more |
| Languages | Multiple language support | 20 languages with community translations |
| Documentation | Modern docs in English primarily | Extensive multi-language documentation |
| Support | Email support with license | Community + paid hosted support |
| Active development | Commercial product roadmap | Community development plus commercial sponsor |
Feature pattern observations:
MailWizz strengths. Modern UI; native drag-and-drop editor; multi-tenant customer accounts; A/B testing as native framework; plugin marketplace; commercial support model.
phpList strengths. Free software; massive established deployment base; longer track record; CMS native integrations; multilingual support; phpList Hosted alternative option; deliverability heritage and focus.
The feature gap favours MailWizz for modern web application patterns and multi-tenant operations; favours phpList for CMS integrations and free software licensing. The choice depends substantially on operator priorities.
CMS integration patterns
phpList's CMS integration advantage deserves specific attention for operators running CMS platforms.
phpList native CMS integrations:
- WordPress. Multiple WordPress plugins for phpList integration: subscription form widgets, automatic post-to-newsletter publishing, subscriber synchronisation between WordPress users and phpList lists, transactional email triggers from WordPress events.
- WooCommerce. E-commerce integration for sending order confirmations, abandoned cart sequences, customer engagement campaigns based on purchase history, customer segmentation by purchase patterns.
- Drupal. Drupal module integrating phpList with Drupal user database, content publishing workflows, comment and engagement triggers.
- Joomla. Joomla extension for phpList integration including subscription management and content publishing.
- Magento. Magento integration for e-commerce email marketing including newsletter signup, order-based campaigns, customer lifecycle messaging.
- PrestaShop. PrestaShop module for e-commerce email integration.
- phpBB. Forum integration for community newsletter and announcement sending.
MailWizz CMS integration approach:
- API-based integration. MailWizz provides comprehensive REST API allowing integration with any CMS through custom code or middleware (Zapier, Make, n8n).
- Limited native plugins. Some MailWizz plugins exist for major CMS platforms but coverage is less comprehensive than phpList's mature integration ecosystem.
- Custom integration typical. Operators needing tight CMS integration typically build custom integration code using MailWizz API rather than installing pre-built integration plugin.
- Webhook-driven patterns. CMS events fire webhooks that MailWizz consumes; standard integration pattern but requires more setup than plug-and-play alternatives.
The CMS integration advantage matters for specific operator profiles:
For operators running WordPress, Drupal, or other major CMS platforms wanting tight email marketing integration without custom development: phpList provides faster initial setup through pre-built integrations.
For operators preferring API-driven integration patterns: MailWizz's flexible API enables custom integration designs matching specific operational requirements.
For operators with simple integration needs (just sending campaigns, no CMS event triggers): both platforms work; the integration difference matters less.
phpList's UI consistently receives feedback about its dated appearance in 2026 reviews. The functional capabilities are present but the visual design and user workflow patterns reflect earlier web application design eras. Specific issues frequently mentioned: cluttered navigation; campaign workflows requiring multiple page transitions; visual feedback minimal during operations; admin interface not optimised for mobile devices; older form-based interaction patterns versus modern reactive interfaces. The UI dating affects operator experience meaningfully: routine campaign creation takes longer than equivalent operations on MailWizz; non-technical users find the workflow less intuitive; visual marketing-oriented users may find the interface aesthetically problematic. phpList project has been updating UI gradually but the architectural decisions limit how much visual modernisation can occur without major refactoring. For operators prioritising modern UI experience, MailWizz produces materially better daily operations despite phpList's other advantages. For operators tolerating utilitarian UI in exchange for free software and other phpList advantages, the UI dating is acceptable trade-off.
Cost comparison
Cost comparison between MailWizz and phpList (self-hosted) and phpList Hosted at typical operational scales:
| Operational scale | MailWizz self-hosted | phpList self-hosted | phpList Hosted |
|---|---|---|---|
| Year 1 small (1K subs, low volume) | $326 ($86 + $240 hosting) | $240 hosting only | $12 ($1/month entry) |
| Year 1 small (5K subs) | $326 + $5 SES = $331 | $240 + $5 SES = $245 | $60-120 (depending on volume) |
| Year 1 moderate (25K subs) | $326 + $30 SES = $356 | $240 + $30 SES = $270 | $240-360 estimated |
| Year 1 large (100K subs) | $566 + $100 SES = $666 | $480 + $100 SES = $580 | $600-1,200 custom |
| Year 2+ small (5K subs) | $245 | $245 | $60-120 |
| Year 2+ moderate (25K subs) | $270 | $270 | $240-360 |
| Year 2+ large (100K subs) | $580 | $580 | $600-1,200 |
| Agency (multi-client) | $275 Extended + hosting = $1,475 | Multi-client requires custom code = $5,000+ effort | Custom enterprise pricing |
Cost pattern observations:
Very small operations. phpList Hosted entry tier ($1/month) cheapest; self-hosted alternatives require minimum infrastructure cost making them less economical at this scale.
Small operations (5K-25K). Self-hosted options become competitive; phpList self-hosted slightly cheaper than MailWizz due to no license cost; phpList Hosted approaches self-hosted total cost.
Moderate operations (25K-100K). Self-hosted clearly cheaper than phpList Hosted; MailWizz versus phpList self-hosted differ by license cost amortisation ($86 over years is minimal).
Large operations (100K+). Self-hosted dominantly cheaper; phpList Hosted pricing approaches commercial alternatives at scale.
Agency operations. MailWizz Extended License substantially cheaper than alternatives; phpList multi-tenant requires custom development; phpList Hosted potentially viable through multiple managed accounts.
The cost comparison shows phpList wins on direct cost only at very small operations and breaks even with MailWizz at typical scales. The cost differential is modest compared to operational considerations.
Operator profile fit
MailWizz and phpList fit different operator profiles.
MailWizz best fits these operators:
- Agencies serving multiple clients. Native multi-tenant architecture with customer accounts; Extended License enables SaaS commercial offering.
- Operations valuing modern UI. Polished admin interface and campaign workflows produce better operational experience.
- Operations wanting A/B testing native. Subject and content testing as platform-native feature.
- Plugin marketplace consumers. Third-party plugin ecosystem provides extensions impossible to easily replicate.
- Commercial software preference. Operators preferring established commercial vendor relationship over open-source community model.
phpList best fits these operators:
- CMS integration users. Operators running WordPress, Drupal, Joomla, WooCommerce wanting tight email marketing integration via pre-built plugins.
- Free software philosophy. Operators preferring open-source licensing for ideological or budget reasons.
- Multilingual operations. 20-language support natively beneficial for non-English operations.
- Long-term reliability priorities. 25+ year project track record with established deployment base provides confidence in continued operation.
- phpList Hosted users. Operators wanting managed hosting at low cost while preserving open-source software path.
- Community participation values. Operators wanting to contribute to open-source community development.
Both platforms work for operators whose needs are covered by core PHP email marketing functionality without specific preferences favouring either platform.
Decision framework
The decision framework for MailWizz vs phpList in 2026:
Use MailWizz when: operating as agency serving multiple clients (native multi-tenant essential); modern UI valuable for operational experience; A/B testing as native feature matters; plugin marketplace ecosystem provides specific needed extensions; commercial software vendor relationship preferred; budget tolerates $86 license cost (operationally negligible).
Use phpList self-hosted when: free software license preferred for philosophical or strict budget reasons; CMS integrations (WordPress, Drupal, etc.) native to phpList provide value; multilingual operations require established multilingual platform; 25+ year track record provides confidence; community-driven development preferred over commercial.
Use phpList Hosted when: very low volume operations (under 1K subscribers) make $1/month managed attractive; want managed hosting plus open-source software path; deliverability consultation from phpList team valuable; flexibility to migrate to self-hosted in future preserved.
Stay on chosen platform when: current platform produces acceptable outcomes; migration cost would exceed remaining benefits; operational discipline established with current platform.
Consider alternatives to both when: non-technical team incapable of self-hosted operations suggests SaaS (MailerLite, Mailchimp); modern Go architecture preferred suggests Listmonk; very high volume (10M+ monthly) suggests dedicated commercial MTA like PowerMTA or KumoMTA; sophisticated automation needs suggest ActiveCampaign or HubSpot.
The 2026 default progression for typical operators:
- Evaluate CMS context: heavy CMS user favours phpList; non-CMS operator considers both equally
- Evaluate UI priority: modern UI essential favours MailWizz; functional UI acceptable allows phpList
- Evaluate agency operations: agency needs favour MailWizz native multi-tenant
- Evaluate budget philosophy: free software preference favours phpList; small license acceptable allows MailWizz
- For very low volume: phpList Hosted $1/month entry tier provides interesting third option
A non-profit client we worked with through 2024 illustrates a common migration pattern: phpList legacy installation to MailWizz. They had been running phpList since approximately 2010 (14 years of phpList use) on legacy hosting infrastructure managing approximately 35K subscribers across multiple programmes. The installation worked reliably but accumulated technical debt: phpList version was several major versions behind current; PHP version on hosting was end-of-life; UI was difficult for new staff to learn; multi-programme management was awkward through phpList's list-based approach. We evaluated migration paths: stay on phpList (upgrade phpList plus infrastructure); migrate to phpList Hosted (managed but loses customisations); migrate to MailWizz (modern UI plus multi-tenant for programme separation). Chose MailWizz migration. Project cost: approximately $8,000 (consulting, MailWizz deployment, phpList data export and MailWizz import, template recreation, automation setup, staff training across multiple programme managers). Migration timeline: 10 weeks including parallel running. Post-migration benefits: modern UI dramatically reduced training time for new staff (from weeks to days); multi-tenant customer accounts isolated programme management; A/B testing improved campaign performance; modern templates improved visual quality of communications. The lesson: phpList legacy installations frequently migrate to MailWizz when modernisation pressure accumulates. The migration justifies the $86 license cost through operational improvements rather than direct cost savings; the modernisation benefit is the lever, not cost optimisation. Operators on aged phpList installations should evaluate modernisation as ongoing operational improvement rather than waiting for crisis.