Weave Code
Beautymail Laravel Package
snowfire/beautymail
Beautymail is a Laravel package for sending beautiful, responsive HTML emails. It provides customizable Blade email templates and themes, inlines CSS automatically, and integrates smoothly with Laravel Mail for consistent transactional emails.
Send beautiful HTML emails with Laravel
Frequently asked questions about Beautymail
- How do I install and configure Beautymail in Laravel?
- Install it with Composer using snowfire/beautymail; Laravel auto-discovery registers the service provider and facade. Publish the config and Blade views with vendor:publish, then send mail through Beautymail::send using your existing Laravel mail transport configuration. You can send a first templated email quickly, but review the published templates before using them in production.
- Which Laravel and PHP versions does Beautymail support?
- The package is a fit for Laravel 8 through 12-era applications on PHP 8.x, but you should verify the exact Composer constraints for your version. Check the illuminate/* and PHP requirements in composer.json rather than assuming parity with every Laravel major. Run a CI matrix against your Laravel and PHP combination before committing.
- Does Beautymail inline CSS automatically for HTML emails?
- Yes, Beautymail uses tijsverkoyen/css-to-inline-styles to inline CSS in the Blade email templates. That improves consistency across many email clients, but it does not fully solve Outlook rendering, Gmail clipping, dark mode, image blocking, or accessibility. Treat the templates as a starting point and test real messages in target inboxes.
- Can I customize Beautymail templates and add my own branding?
- Yes, publish the views into resources/views/vendor/beautymail and commit them as first-class source rather than leaving them as vendor artifacts. You can customize the supplied Blade templates or use them as layouts for your own email views. The template set is the real product, so plan a brand and email-client rendering review.
- How is Beautymail different from Laravel Mailables or Markdown mail?
- Beautymail is an alternative rendering path beside Laravel's Mail and Mailable stack, not a replacement for Mailables, Notifications, or Markdown mail. Its API mirrors Mail::send, while the value is in the responsive Blade templates and automatic CSS inlining. Adopting it can create a second convention for sending email unless you wrap it behind an internal mailer.
- Does Beautymail support queued emails, attachments, and localization?
- Those concerns are not fully handled by the Beautymail facade itself; queueing, localization, attachments, and per-tenant branding need your own conventions around it. Native Mailables and Notifications provide those features more directly. If you need them, define a thin internal wrapper that owns these behaviors before rolling Beautymail out broadly.
- Is Beautymail safe to use in production and actively maintained?
- It is a single-maintainer, small-codebase package with historical release-cadence gaps; a 2025 release is a positive signal but not a guarantee of Laravel-major parity. Budget for a fork or for vendoring the views into your repository if the package lags. The low abstraction depth limits migration risk, but you still own the rendered email surface and should test it in CI and real inboxes.
- Can Beautymail work with SMTP, SES, Postmark, or Mailgun?
- Yes, Beautymail composes with Laravel's existing mail transport configuration, so SMTP, SES, Postmark, and Mailgun do not require infrastructure changes. Its send signature mirrors Mail::send, making it a thin rendering path over the configured transport. Confirm your provider configuration remains untouched when adopting the package.
- How do I migrate away from Beautymail later?
- Wrap Beautymail::send behind an internal Mailer or service so call sites never reference the package directly. Because the abstraction is thin and the templates are Blade files, replacing it with native Mailables plus your own templates is usually a contained migration measured in days, not a re-platforming. Migrate one low-risk transactional email first, then move templates one at a time.
- What are alternatives to Beautymail for Laravel HTML emails?
- Alternatives include native Laravel Mailables or Markdown mail, provider-hosted templates such as Postmark, SendGrid, or SES, and headless email-design tools. Choose based on whether you want design control in the repository or template management delegated to a provider. Beautymail is strongest when a Laravel app needs branded transactional email without a separate ESP template pipeline.
Weaver
How can I help you explore Laravel packages today?