DocuSign Bulk Send: How It Works, Limits, and What It Costs

DocuSign bulk send takes one template and sends a separate, personalized copy of it to everyone on a recipient list you upload as a CSV. Each person gets their own envelope, signs only their own document, and never sees anyone else's. It lives on DocuSign's higher plan tiers, and the detail that catches most teams out is that a bulk send to 300 people consumes 300 envelopes, not one.

Last updated July 2026. Plan names, prices, and feature gates change; the limits below come from DocuSign's own developer documentation, but check your account settings and docusign.com/pricing for what your specific subscription includes.

What is bulk send in DocuSign?

Bulk send is a DocuSign feature that mails one template to many recipients at once, generating an individual envelope for each person on your list. You upload a CSV or XLSX of names and email addresses, DocuSign merges each row into its own copy of the template, and every recipient signs privately. It replaces the alternative of creating and sending envelopes one at a time.

The typical use cases are the ones where the same document goes to a whole group: annual policy acknowledgments, updated terms for a customer base, W-9 collection from a vendor list, open enrollment forms, or onboarding paperwork for a new cohort of hires. Anything where the text is identical and only the signer changes is a candidate.

What bulk send is not is a mail merge for different documents. One bulk send batch carries one template. If half your list needs a contractor agreement and the other half needs an employee packet, that is two separate batches.

How does DocuSign bulk send work?

The workflow has four steps. You build a template with the signature and data fields you want, mark the recipient role as a bulk recipient, upload a CSV where each row is one signer, then send the batch. DocuSign queues the envelopes and delivers them, and you track the results from a bulk send status view rather than the normal envelope list.

A few things about that sequence matter in practice. The template has to be finished before you start, because bulk send will not let you place fields mid-flight. The CSV column headers have to match what DocuSign expects for recipient name, email, and any custom merge fields you added to the template. And the batch processes asynchronously, so a large send will trickle out over minutes rather than landing all at once.

Custom fields are where bulk send earns its keep. If your template has a text field for, say, a territory or a start date, you can add a matching column to the CSV and each recipient's copy arrives pre-filled with their own value. That is the difference between a genuine merge and just emailing the same PDF to a distribution list.

What is the DocuSign bulk send limit?

DocuSign caps each bulk send batch at 1,000 records and limits an account to 2,000 queued bulk send records at a time. Its developer documentation states plainly: "Docusign limits each batch to no more than 1000 records. Each record means each envelope." DocuSign also recommends keeping batches nearer 500 records for faster processing.

Here are the constraints worth knowing before you plan a large send:

The account queue limit is the one that trips up large operations. You can submit a 1,000 record batch, but if you fire three of them back to back you hit the 2,000 ceiling and the third waits. For a genuinely large annual mailing, plan on staging the batches over a few hours rather than queueing everything at nine in the morning.

Does DocuSign bulk send count as one envelope?

No. Each recipient in a bulk send becomes its own envelope and draws down your envelope allowance individually. A single bulk send to 250 people counts as 250 envelopes, not one. DocuSign's documentation is explicit that each record in the batch means one envelope, and billing follows the same rule.

This is the single most expensive misunderstanding in DocuSign bulk send, because the feature feels like one action. You click send once. But if your plan includes a fixed envelope allowance per user per year, one moderately sized bulk send can consume the entire year's allotment in an afternoon. Teams discover this when the next envelope fails to send in October.

The arithmetic is worth doing before you upload the list:

If your plan is on an allowance rather than unlimited sending, check the remaining balance before a bulk send, not after. And if you are billed monthly rather than annually, look closely: DocuSign's monthly terms have historically been more restrictive on envelope volume than the equivalent annual plan.

How many envelopes does a bulk send actually use?

One per data row, and the header row is not a row. DocuSign's envelope allowance FAQ, updated August 11, 2026, puts it in plain arithmetic: "a file with 100 rows creates 99 envelopes (the headers row at the top does not count as an envelope). Each of the 99 envelopes counts toward the allowance."

That is the single most useful number on this page, because it turns bulk send from a feature into a budget line. A Standard seat carrying roughly 100 envelopes a year is one 100 row bulk send and nothing else for twelve months.

DocuSign also confirms that if the bulk send fails, no envelopes are generated and none count against your allowance, so a rejected upload is not a charged mistake. What is charged is a successful send to a bad list. Validate email addresses before you upload, not after.

Why am I seeing an Envelope Allowance Exceeded error?

Because the plan's send allowance for the current period is used up, which is the ordinary case, or because of one of three things DocuSign lists that catch people right after they pay. The first is temporary fraud prevention limits on new accounts. The second is an incomplete billing address on the account profile. The third is cached browser data from before the plan change.

DocuSign's fix for the last three is mechanical: sign out and close all browser windows, clear cache and cookies for all time, sign back in and complete every billing address field including first and last name, street, city, state, postal code and country, save, then try again in a private window. It also notes that a new purchase can take about 30 minutes to fully activate and that you have to click the link in the welcome email before the account stops behaving like a trial.

Worth knowing that even a large allowance is not a blank cheque. DocuSign states that send volume is subject to its Reasonable Use Policy and that it may prevent you from sending new envelopes if your volume exceeds it. If bulk send is central to how you operate, get your expected volume in front of a salesperson before you commit to an annual contract.

How much does DocuSign bulk send cost?

Bulk send is not sold separately. It is bundled into DocuSign's Business Pro tier and above, so the cost is the cost of that plan, charged per user per month. Published 2026 figures for Business Pro on annual billing sit in the $40 to $45 per user per month range depending on the source, and DocuSign revises this schedule regularly.

Two things make the real bill higher than the sticker price suggests. First, it is per seat: bulk send is an account-level need, usually driven by one or two operations people, but the plan is priced per user, so a five person team pays five times over to give two of them the feature. Second, envelope consumption is per recipient, as above, so heavy bulk senders can push past their included volume and pay for overage on top of the seats.

We keep a maintained breakdown of the tiers and what each one actually includes on our DocuSign pricing page, and a broader side by side of the major vendors on the e-signature pricing comparison. If the per-seat model is the sticking point rather than the product, the DocuSign alternatives worth looking at are the ones priced per account.

For context on the other side of that trade: SignSend prices per account rather than per seat, with no separate envelope meter, and bulk send to a recipient list is included on its Business plan. That is still the honest comparison to run, because for a small team sending a few hundred documents a year the seat count usually matters more than the feature list.

How do you create a DocuSign bulk send CSV template?

Download the sample CSV from the bulk send screen rather than building one from scratch. DocuSign generates it with the exact column headers your template expects, including a column for each custom field you added, so the merge maps correctly on the first attempt. Fill in one row per recipient and upload it back.

The failures are almost always formatting rather than content. Column headers that were edited or reordered break the mapping. Trailing blank rows create empty envelopes that then sit in your queue as errors. Email addresses with stray whitespace fail validation for that row while the rest of the batch goes through, which is worse than a clean failure because it is easy to miss.

Before you send a list of any size, run the batch with three test rows pointed at addresses you control. Open all three, confirm the merge fields resolved to the right values, and only then upload the real list. Ten minutes of testing beats recalling 400 envelopes with the wrong start date in them.

Why is DocuSign bulk send not available in my account?

The usual reason is the plan. Bulk send appears on Business Pro and higher, so accounts on Personal or Standard will not see the option no matter where they look. The second reason is permissions: even on a qualifying plan, an administrator has to enable bulk send for the account and grant it in the user's permission profile.

If you are on the right plan and still cannot find it, check three places in order. Account settings for the sending permission itself, your user permission profile for whether bulk send is allowed for you specifically, and the template, because the feature only surfaces once a recipient role has been marked as a bulk recipient. The option is genuinely hidden until that last step is done, which sends a lot of people to support unnecessarily.

Can you bulk send different documents to different people?

Not within a single batch. One bulk send carries one template, so every recipient in that batch receives the same document with only the merged field values differing. To send genuinely different documents you create one template per document and run a separate bulk send for each recipient group.

There is a partial workaround. If the documents differ only in a clause or two, you can sometimes build one template with conditional fields and drive the variation from CSV columns. That works for a paragraph that appears or does not. It does not work for two structurally different agreements, and trying to force it produces a template that nobody can maintain six months later.

When bulk send is the wrong tool

Bulk send suits identical documents going to a known list. It is a poor fit for three situations worth naming. Negotiated agreements, where each counterparty will redline, need individual envelopes anyway. Sequenced workflows, where an internal approver signs before the counterparty, get complicated fast inside a bulk batch. And ongoing collection, where new people join a list continuously, is better served by a link or an API call per person than by periodic batches.

That last one is worth flagging for anyone automating. If your real need is "send this document whenever a new person signs up," you want an e-signature API firing one request per event, not a nightly bulk job. Bulk send is a batch tool, and batching an event stream adds latency for no benefit.

The same logic applies to hiring. Bulk send handles the annual handbook acknowledgment for existing staff well. For a rolling stream of new hires, per-event sending through onboarding document e-signature or an offer letter signing flow fits the actual shape of the work better. And if you are sending the same offer letter to a whole cohort at once, the bottleneck upstream is usually screening and ranking the candidates rather than the signature step itself.

The short version

Bulk send is a solid feature that does exactly what it says: one template, many recipients, one envelope each. Plan around three numbers and you will not be surprised. Batches cap at 1,000 records, accounts cap at 2,000 queued records, and every recipient costs you one envelope against whatever allowance you have.

The question worth asking before you commit to it is whether you are buying the feature or the pricing model. If bulk send is the one thing you need from a higher tier, and you are paying per seat across a team to unlock it for two people, the math often favors a tool that prices per account instead. If you genuinely need batch sending, DocuSign's Business Pro is one way to buy it; SignSend includes bulk send to a recipient list on its $29 Business plan, and keeps a full audit trail on every document either way.

Is there a size limit on a DocuSign bulk send?

Yes, and it is tighter than the normal one. DocuSign caps a standard envelope at 200 MB in total, but an envelope being bulk-sent cannot exceed 75 MB. The individual document limits still apply on top of that: 50 MB per document in the web app, 2,000 pages per document, and 130 unique documents per envelope.

This catches people out because the template sends fine as a one-off and then fails the moment it goes into a bulk list. If your bulk template includes a scanned handbook or a set of exhibits, that is almost certainly what is blocking it. Compressing the scan usually solves it in a few minutes. The complete set of caps, including recipient limits and the exact error text DocuSign returns for each, is on our DocuSign limits page.

Does bulk send count against your API allowance?

It depends entirely on how the bulk send is triggered. Start a bulk send from the DocuSign web app and each resulting envelope draws on your web application envelope allowance. Fire the same bulk send through the eSignature REST API and every envelope draws on your automation send allowance instead, which is a much smaller and separately metered pool.

That distinction bites hard because the automation allowance on DocuSign's IAM plans is 100 sends per user per year even where web sending is marked unlimited, and on user-based eSignature plans DocuSign lists automation sends as not included at all. A single 300 recipient bulk list run through the API will exhaust a small team's entire annual automation budget in one afternoon and return an envelope allowance error on a plan whose billing page says unlimited. We unpack that error and the fixes in DocuSign envelope allowance exceeded.

Worth knowing too: bulk send through the eSignature REST API is not available on DocuSign's entry level developer tiers. It appears on the Advanced plan at $480 a month, which carries the same 100 envelope a month allowance as the $300 Intermediate tier. In other words the extra $180 a month buys the bulk send capability, not extra volume. The tier by tier costs are in our page on DocuSign API pricing. PowerForms behave the same way as bulk send here: every submitted form becomes its own envelope against the account.