HomeFeaturesFile sending

File sending

Send the invoice, not a link to the invoice.

A file in WhatsApp is not an attachment on an email. It has to be the right format, under the right size, and fetched by the service rather than pushed to it. Birsend handles all three so a PDF arrives as a PDF and a recording arrives as a voice note.

10 MB
per outgoing file
Two-way
library — what you send and what arrives
Private
by default, never a public URL

What you get

Attach a real document, photo or voice note to a campaign or a single reply — and keep everything customers send you, in one library.

Documents and PDFs

Invoices, tickets, menus, price lists. Up to 10 MB, arriving with the filename your customer will actually recognise.

Images and video

Product photos and short clips preview inside WhatsApp instead of downloading. Large photos are shrunk in the browser before they upload.

Proper voice notes

A recording is converted to the format WhatsApp expects, so it arrives as a voice note rather than as a music player.

Everything customers send you

Photos, documents and voice notes arriving from customers are saved to the same library, browsable and searchable later.

Nothing on a public URL

The library holds your customers’ files. Nothing sits on a guessable address — every download is checked against your workspace.

Confirmed delivery

File messages report the same delivered and read states as text, so you know the document actually arrived.

How it works

01

The library works in both directions

Most tools store what you upload. Birsend also keeps what customers send in — the photo of a damaged parcel, the signed form, the voice note explaining an order — filed against the same library and the same contact.

  • Filter by kind: image, video, audio, voice note, document, sticker
  • The same upload shared by several messages is stored once
  • Deleting a file that a message used hides it from the library and leaves the message intact
02

Sent from the library, not from the composer

A file is uploaded first and sent second. That split is deliberate: an upload can be slow and can fail on its own terms, and tying it to the send would make a failed conversion look like a failed message.

  • Images are optimised in the browser before upload, so a phone photo fits
  • The WhatsApp service fetches the bytes itself, from a signed address that expires
  • Which endpoint is used depends on what the file is — to WhatsApp a photo and a document are different messages

What it does not do

The honest list. We would rather you found this here than three weeks into a trial.

  • 10 MB per outgoing file, and WhatsApp’s own per-kind limits are lower still for video.
  • One file per message. There are no albums, catalogues or multi-item cards.
  • Every recipient of a campaign gets the same attachment. Per-contact documents — their invoice, their ticket — are not supported.
  • Captions are sent as written; they carry no merge fields.

Questions

Where are the files kept?

On our server, scoped to your workspace, served only to signed-in members of it. Nothing is placed on a public disk, because the library holds your customers’ documents as well as your own.

Can I reuse a file across campaigns?

Yes. Upload once and pick it from the library each time; identical uploads are stored once.

Cookies

The site runs what it needs to work, including the Crisp chat bubble. Google Analytics is the one thing we will not load unless you agree to it.