Mail merge with attachments
that actually attaches the file.
Word can't attach it. Gmail caps you at 500 a day. Pictify generates a personalized PDF from every spreadsheet row and emails it to each recipient — with per-person delivery status.
Why "mail merge with attachments" is a search without a good answer
Every tool in the usual toolkit stops one step short of the inbox.
Word mail merge
Cannot attach the fileThe merged text becomes the email body. There is no attachment option — and the file is the whole point.
Gmail / Workspace merge
500–1,500 emails per dayFree Gmail caps at 500/day, Workspace mail merge at 1,500/day — and locks you out mid-batch when you hit it.
Sheets add-ons (Autocrat & co.)
6-minute timeouts, your Gmail quotaApps Script executions cap at 6 minutes and sends ride your own Gmail. Google's June 2026 runtime migration broke add-on merges across an 81M-install base.
Design tools (Canva)
Stops at downloadBulk Create makes the variants, then hands you a zip. No email delivery of any kind — distribution is still your job.
Stop attaching. Start delivering.
The attachment hack exists because your document tool and your email tool are two different tools. Pictify is one run: each CSV row renders into its own personalized PDF, and each PDF goes to its recipient from an isolated sending domain — not your Gmail. What you get back isn't "sent". It's delivered, per person, with bounces suppressed automatically and any row re-sendable in one click.
- ✓ Personalized PDF per row — not one file for all
- ✓ No Gmail daily caps, no mid-batch lockouts
- ✓ Delivered / bounced / complained, per recipient
- ✓ Fix a bad address, re-send that one row
CSV in. Inboxes reached. Three steps.
Upload your spreadsheet
Export your list as CSV — one row per recipient with an email column — and drop it into a Pictify workflow.
Pick or generate a template
Choose a document template or describe one to the AI Template Maker. Map CSV columns to the template variables.
Run and watch delivery
Every row renders to its own PDF and emails to its recipient. The run screen shows delivered, bounced, or suppressed per person, with one-click re-send.
Every row rendered. Every recipient reached. Provable.
Delivery is part of the run
Every row renders AND emails to its recipient from an isolated sending domain. Your job ends at delivered, not downloaded.
Per-row proof
Sent, delivered, bounced, complained — per person, via real ESP webhooks. A bounce is a one-click re-send with a corrected address.
One engine, every deliverable
Certificates, badges, tickets, reports, personalized video — the same template and data contract renders PNG, PDF, GIF, and MP4.
Real expression engine
{{ price * 0.9 | currency }} is a first-class template feature. Conditionals, filters, loops — logic lives in the template, not your backend.
Wizard + API + agents
Organizers run the wizard. Developers sign a webhook. AI agents author templates over MCP. Same template, same run history.
AI Template Maker
Describe the document or video and get an editable HTML-native template with your brand and variables in place.
Frequently asked questions
Can Word mail merge send attachments? +
No. Word's built-in mail merge sends the merged text as the email body — it has no option to attach a file, personalized or otherwise. When the deliverable IS a file (a certificate, an invoice, a report), the built-in merge cannot do the job. Pictify generates the personalized PDF per row and sends it as a real attachment-style delivery: each recipient gets a personal email carrying their own document.
What are the Gmail mail merge limits? +
Gmail caps sending at 500 emails per day on free accounts and 1,500 per day via Google Workspace mail merge — and it can lock you out mid-batch when you hit the cap. Every merge add-on that sends "from your Gmail" inherits these limits. Pictify sends from its own isolated sending domain, so your batch size is your plan's email quota, not Gmail's daily cap, and your personal sender reputation is never at stake.
How do I mail merge a personalized PDF to each recipient? +
Upload a CSV (one row per recipient, with an email column). Pick or generate a document template — the AI Template Maker builds one from a text description. Map columns to template variables, send a test to yourself, then run. Each row renders to its own PDF and emails to its recipient. The run screen shows sent, delivered, or bounced per person.
What happens when an address bounces? +
The row shows bounced with the reason, the address is automatically suppressed so future runs never burn a send on it, and you can correct the address and re-send that single row — no re-running the whole batch, no bounce spreadsheet.
Do recipients see a generic bulk sender? +
Sends go out from Pictify's dedicated sending infrastructure with your name on the message; paid workspaces get their own isolated sending subdomain. Every message carries a compliant one-click unsubscribe, which protects your deliverability instead of hurting it.
Can I trigger the merge automatically instead of uploading a CSV? +
Yes. Every workflow exposes a signed webhook — point your form tool, LMS, CRM, or a Zapier/Make/n8n flow at it and each payload renders and delivers one document. The CSV wizard and the webhook feed the same template and the same run history.