What is the best way to send an ecard for free?

Pick the delivery channel first based on who it is for and what the occasion is. Email works for cards the recipient will want to sit with, text works for cards where the timing matters most, and a share link works for any group card with more than three signers. Most major ecard platforms offer all three options for free; the choice that decides whether the card lands is which one you pick, not which platform.

Can I send an ecard as a text message?

Yes, most ecard tools support text delivery, and it works well for short, light occasions where the moment is the gift. A same-day birthday wish, a quick congratulations on a job offer, a get-well text the morning after surgery. Avoid text for sympathy cards, heavy farewells, or anything where the recipient should be able to sit with the message without a notification banner pushing it off the screen.

Can I send an ecard to multiple people at once?

There are two ways to read this question. If you want one ecard signed by many people for a single recipient, use a group ecard with a share link and let everyone sign before delivery. If you want the same ecard sent to several recipients individually (like a holiday card to a friend list), most platforms support either bulk-email addressing or duplicating the card and resending. The first case is far more common.

Do I need an account to send an ecard?

On most platforms, you need an account to create and schedule the card, but recipients do not need an account to view it, and signers usually do not need one to add their message. This matters more than it sounds: requiring signup at the sign step drops participation in a group ecard by roughly half. Pick a platform that lets signers contribute without an account.

How do I schedule an ecard to arrive on a specific day?

Most ecard tools have a scheduling step at delivery setup where you pick the date and time, and the platform handles the rest. The detail to get right is the recipient's time zone, not yours. A 7am delivery scheduled in your time zone can land at 4am theirs, which is worse than not scheduling at all. Pick the moment in their day you want the card to arrive, then back-calculate.

What is the difference between an ecard and a regular email?

An ecard is a designed, often interactive greeting delivered through a card tool that handles the cover, the message layout, and (for group cards) the signature collection. A regular email is just text and maybe an attached image. The visual structure and the optional multi-signer flow are the real difference; the underlying delivery mechanism (email, SMS, or a hosted URL) is the same either way.

All articles

Ecards

How to Send an Ecard (Email or Text)

Sarah Whitfield

May 25, 2026

A friend of mine spent thirty minutes last spring building a sympathy ecard for her boss, then sent it as a text message to his work number. He read it on his phone, in the parking lot of the funeral home, while walking in. She told me later she still cannot think about that without flinching. The card itself was fine. The delivery channel was wrong. Most of the advice you will find on how to send an ecard skips this part entirely and walks you through the same generic recipe regardless of what the card is or who it is going to. That is the part I want to fix.

Start a group card in 30 seconds

Free. No signup needed.

Jump to section11 sections

The question isn't how. It's which channel.

Every other article on this topic opens with a numbered list that looks roughly like: pick a card, type your message, enter the recipient's email, hit send. That recipe is fine if you already know which delivery method you should be using. Most people don't, and the wrong one quietly ruins an otherwise good card. A birthday ecard sent to a work email gets opened on a Slack break between meetings, scanned, and forgotten. A condolence ecard sent as a text arrives next to an Uber Eats notification. A group farewell ecard sent as a share link in a Slack channel gets one signature because nobody clicks links in Slack channels.

So before the mechanics, the harder question: who is this for, and where do they actually read the things that matter to them? The rest of this piece is built around that question. I'll walk through the three channels (email, text, share link), name the scenarios each one wins, and then cover the actual sending step at the end where it belongs.

Email wins when the moment can wait

Email is the default for a reason: the inbox is the closest thing most adults have to a mailbox, and it forgives a slightly longer message in a way a text never will. Use email when the ecard is for something the recipient will want to sit with rather than glance at. Birthdays for friends and family. Work anniversaries. Thank-you notes that name specific things. Anything condolence-shaped going to a personal email address (not a work one, ever, for sympathy).

The other thing email does well: it shows up as a single, contained event. The recipient opens an email, sees the cover, scrolls through the messages, closes the tab. There is no notification scroll burying it three minutes later. For a group card with eight or fifteen signed messages, this matters more than people realize. Texts are designed for the next message to push the previous one off-screen. A heartfelt card is the opposite of that traffic pattern.

Practical note that nobody mentions: send personal-occasion ecards to the recipient's personal email, not their work one, even if you only have the work address. Track down the personal one. It takes ninety seconds and changes how the card lands. The work inbox has the wrong emotional context, and corporate spam filters will sometimes hold ecards from unfamiliar senders for hours.

Text wins when the moment is now

Text beats email when the timing is the gift. A same-day birthday wish to your sister at 7am her time. A congratulations the minute someone posts their engagement. A get-well text the morning after surgery, when the recipient is at home and bored and refreshing their phone. These are moments where a delayed inbox arrival would be worse than a quick text card delivered the second they wake up.

Text also wins for shorter, lighter cards. A funny birthday card to a college friend. A quick thank-you to the neighbor who watched your dog. Anything that should feel casual and not like a Hallmark production. If the relationship is the kind where you'd send a meme rather than a paragraph, the ecard should arrive in the same channel as the meme.

The risk: text strips the emotional weight off anything serious. If the card is for a sympathy moment, a hard medical update, a farewell where the recipient is genuinely sad to be leaving, text is the wrong channel almost regardless of how close you are. The notification arrival cheapens it. I have learned this the hard way and now have a rule: if I am writing the card with any care about word choice, it goes by email or share link, not by text.

The third option, and the one most people forget exists, is just sending the ecard as a link in whatever chat the group is already in. Slack channel for a coworker's farewell. WhatsApp family thread for a parent's milestone birthday. Group iMessage for the close-friends-only birthday card. The card lives at a URL; you send the URL; people open it and sign on their own time; the finished thing gets delivered to the recipient as a single email or text at the moment you set.

This is the only delivery method that works for a card with more than three signers. Email gets you one chance to invite each person and a per-email-platform spam risk. Text is awful for coordinating fifteen signatures because nobody is going to copy-paste a link from a text into their browser. A share link in the group's existing chat thread is where they already are, and it puts the social pressure to sign right where it should be: visible to the rest of the group.

The pattern I use: build the group ecard with multiple signers first, sign it myself with a longer specific message, then paste the link into the relevant chat with one sentence about what it is. The first message I add sets the tone for everyone else, which is also why which ecard platform you pick matters less than people think; the messages inside carry the card, not the brand on the cover.

Step 1: Pick the channel before you pick the card

I know this is backwards from how every card tool walks you through it. Decide the delivery channel first anyway, because the channel constrains the card. A short text-delivered ecard wants a punchy cover and a one-line greeting. An email-delivered card for a milestone moment can hold a longer message and a slideshow of photos. A share-link group card needs a layout that looks good with fifteen signatures on it, not one.

Most card platforms make this decision look like a final step ("choose how to send"), which is why it goes wrong. Make it the first step instead. Ask the question: am I doing this solo or as a group, is the moment immediate or delayed, is the register heavy or light, is the recipient going to read this on a phone in line at the grocery store or in their inbox once the workday ends. The answer tells you the channel. The channel tells you which card to build.

Step 2: Build the card to match the channel

For email-bound ecards, lean into length. A single static cover, a real message of three to five sentences, maybe a photo. Email forgives a slightly slower reveal. The recipient is not being interrupted by a notification; they have already chosen to open this. For text-bound ecards, the cover does most of the work. A single sharp image, a one-line greeting, maybe one short signed note. The recipient sees the preview thumbnail before they tap the link, and the thumbnail has to land in that one second.

For share-link group cards, build the card with the eventual signature count in mind. A board layout (the post-it style) holds more visible signatures at a glance than a multi-page greeting card. A multi-page card feels more personal but works best when you have four or five signers, not twenty. If you are not sure which to pick, a group card online with multiple signatures in board layout is the safer default for any group above six people.

Step 3: Write your message first, before inviting anyone

Whether it is a solo card or a group one, the first written message sets the standard for whatever comes after, even if the only "after" is the recipient opening it. If you are signing alone, your message is the card. If you are inviting a group, your message tells the other signers what register is expected. A short generic line invites short generic lines. A specific message naming a real moment invites the same in response.

I have a soft rule: never invite the group to a card I have not already signed. Six minutes of writing a real first message saves the awkward situation of the recipient opening a card where the only message is from the colleague who joined the team last month and barely knows them. Sign first. Invite second.

For email delivery, type the recipient's email address. Use the personal one if you have it; see the section above for why that matters. For text, enter the phone number. For share-link delivery, generate the URL and paste it into the group's chat. The mechanics are the same across most card platforms and are usually the easiest part of the whole process. You can create a card online in a few minutes and have all three options available at the delivery step.

One sub-step worth flagging: for email and text delivery, set the delivery time. Do not send the card the moment you finish it unless the moment of finishing matches the moment of arrival you want. Most birthdays should arrive in the recipient's morning, not at 11pm the night before. Most sympathy cards should arrive a day or two after the news, not in the first chaotic hour. Most thank-you ecards work best in the morning of the day after the favor, not the same evening.

Step 5: For group cards, send the link with a sentence

If you are coordinating a group, this is the step that decides whether you end up with four signatures or eighteen. When you paste the share link into the chat, write one sentence with it. "Maria's last day is Friday, signing a card, please write something specific." That last word, specific, does maybe a third of the work by itself. People want to write something good; most of them are just not sure what is expected. Telling them earns you better notes and more of them.

The other move: send the link to the small inner-circle group first. Let three or four real messages land on the card. Then forward the link to the wider circle. The early signers set the standard for the late signers, and by the time the wider circle opens the card there are already real-feeling messages on it to match.

If you remember nothing else: email for cards that deserve a slow read, text for cards where the timing is the gift, share link for any card with more than three signers. Picking the wrong channel can sink a card you spent half an hour writing. Picking the right one buys forgiveness for a slightly weak message. Almost no other guide on this topic will tell you that, because the templated recipe is easier to write. The templated recipe also produces sympathy cards delivered as texts to funeral-home parking lots, which is the thing I am still trying to undo with this article.

Turn it into a group card

Most ecards worth sending past the age of about ten are group ecards. The geometry just works better: more voices, less pressure on any one signer to be profound, and a finished thing that feels like a small archive of how people actually feel about the recipient. The reason solo ecards have such a templated reputation is that one person writing one message in a card tool tends toward the generic. Six people writing six different specific messages does the opposite work.

For workplace occasions, a group birthday card online or a farewell ecard with the team signing is the easiest version of this. One link goes to the channel, each person writes on their own time, and the recipient gets a single delivery at the moment you scheduled. You can create a card online in a few minutes, pick the channel (email to the recipient, share link to the signers), set the delivery time, and walk away. The card collects itself while you do other things.

For the message side of it, the cluster pieces on happy birthday wishes for a coworker and what to write in a baby shower thank-you card have specific examples you can crib from when stuck. If you are sending a thank-you ecard for a wedding or a baby gift, the latter has the format I use that does not sound like a form letter.

One last thing, off-topic and probably only useful to me. I keep a running note on my phone called "channel mistakes" that I have not opened in about eight months but that contains, in chronological order, every time I have sent the wrong type of message through the wrong delivery channel. The sympathy text to my friend's boss is in there, second from the top. The funny birthday card I emailed to a friend's spam folder where it sat for nine days is in there. The voice memo I sent to my mother that was meant for my brother and contained, fortunately, no incriminating content but also did not make any sense to her is in there. The note is mostly useful as a reminder that the channel is part of the message, not a wrapper around it, and that I will keep getting that wrong forever in small ways. I think that is fine. The note is also a kind of card to my future self, written in the wrong tone for the channel, which is probably also fine.

Frequently asked questions

What is the best way to send an ecard for free?: Pick the delivery channel first based on who it is for and what the occasion is. Email works for cards the recipient will want to sit with, text works for cards where the timing matters most, and a share link works for any group card with more than three signers. Most major ecard platforms offer all three options for free; the choice that decides whether the card lands is which one you pick, not which platform.
Can I send an ecard as a text message?: Yes, most ecard tools support text delivery, and it works well for short, light occasions where the moment is the gift. A same-day birthday wish, a quick congratulations on a job offer, a get-well text the morning after surgery. Avoid text for sympathy cards, heavy farewells, or anything where the recipient should be able to sit with the message without a notification banner pushing it off the screen.
Can I send an ecard to multiple people at once?: There are two ways to read this question. If you want one ecard signed by many people for a single recipient, use a group ecard with a share link and let everyone sign before delivery. If you want the same ecard sent to several recipients individually (like a holiday card to a friend list), most platforms support either bulk-email addressing or duplicating the card and resending. The first case is far more common.
Do I need an account to send an ecard?: On most platforms, you need an account to create and schedule the card, but recipients do not need an account to view it, and signers usually do not need one to add their message. This matters more than it sounds: requiring signup at the sign step drops participation in a group ecard by roughly half. Pick a platform that lets signers contribute without an account.
How do I schedule an ecard to arrive on a specific day?: Most ecard tools have a scheduling step at delivery setup where you pick the date and time, and the platform handles the rest. The detail to get right is the recipient's time zone, not yours. A 7am delivery scheduled in your time zone can land at 4am theirs, which is worse than not scheduling at all. Pick the moment in their day you want the card to arrive, then back-calculate.
What is the difference between an ecard and a regular email?: An ecard is a designed, often interactive greeting delivered through a card tool that handles the cover, the message layout, and (for group cards) the signature collection. A regular email is just text and maybe an attached image. The visual structure and the optional multi-signer flow are the real difference; the underlying delivery mechanism (email, SMS, or a hosted URL) is the same either way.