# Resend overview

`@workermailer/resend` is the Worker Mailer package for teams that want the Resend API instead of raw SMTP, while keeping a familiar message model shared with `@workermailer/smtp`.

## Why use the Resend package

This package keeps delivery simple for Worker apps that already use Resend for domains, sender identities, and analytics. It speaks HTTP with `fetch`, which makes it a lighter fit than direct SMTP when you do not need socket-level control.

## What ships today

- Cloudflare Worker-friendly delivery with `fetch`
- TypeScript message types aligned with the SMTP package
- Plain text and HTML bodies
- Attachments passed through to Resend
- Queue helpers for Cloudflare Queues
- EmDash sandbox bundle in `emdash-plugin/`

## SMTP alignment

The main API shape mirrors the SMTP package on purpose:

- `connect()` returns a mailer object
- `send()` exists as both an instance method and a static helper
- queue helpers use the same producer and consumer pattern

That makes it easier to switch or support more than one delivery provider across the same Worker codebase.

## When to choose Resend

Choose `@workermailer/resend` when you:

- already use Resend as your email provider
- want a fetch-based delivery flow without direct SMTP handling
- prefer provider-managed infrastructure over raw socket transport

## Where to go next

- Start with [Installation](/docs/resend/installation)
- Send a message in [Quickstart](/docs/resend/quickstart)
- Move async delivery to [Queues](/docs/resend/queues)