What 'digital greeting card' actually means

The phrase covers three completely different things, and most how-to articles smear them together as if they were one product. They are not. Picking the wrong format is, in my experience, the failure that wrecks more of these cards than any design decision ever does.

The three formats, plainly. One: a single-page ecard. One cover image, one message inside, sometimes a short animation. Opens in five seconds, gets read in twenty. Smilebox, JibJab, and most of the legacy ecard sites do this. It is what most people picture when they hear 'ecard'. Two: a multi-page flip card, where the recipient lands on a cover, taps to open the envelope, and pages flip in 3D like a real card on a shelf. Three to six pages, usually, with one signer per page or a few signers grouped per page. This is the format Reco is unusual for offering, and it is the closest digital experience to the feel of opening a physical card. Three: a group board, where many people sign one shared page, sticky-note style, with each note adjustable in position and color. Kudoboard and GroupGreeting do this. It scales to twenty or fifty signers without the format breaking.

Three formats, three different recipients, three different occasions. The article most other sites publish gives you generic five-step instructions that would only work cleanly for one of the three. This article picks the format question apart first.

Most people want a single-page ecard, not a multi-page one

This is the inconvenient truth nobody publishing about digital greeting cards seems willing to say. When someone searches 'how to make a digital greeting card', the picture in their head about three quarters of the time is the single-page ecard: a cover, a message, hit send, done. They are not picturing a 3D-flip multi-page experience. They are picturing the digital equivalent of the paper card on the kitchen counter at a birthday breakfast.

Reco is built around the multi-page format as a differentiator, and we believe in it for the right occasions. But pretending it fits every occasion is the kind of overselling that wastes the reader's afternoon. The multi-page flip is overkill for a quick thank-you, for a 'thinking of you' to a sick coworker, for a birthday card from one parent to one adult child. For those, the single-page ecard format wins, and we still offer it, because the right answer is sometimes the simpler one.

The multi-page format earns its keep on larger, slower occasions. A milestone birthday for somebody who will actually open the link on a laptop with twenty quiet minutes. A retirement card where each page belongs to a different chapter of the person's career. A wedding card where the cover, the toast, and the joint photo each want their own space. A condolence card where the slow flip itself becomes part of the gentleness. Those are the cards that genuinely benefit from the flip; the rest read better as one page.

If you are still on the fence, here is the question I ask myself before building: would the recipient probably open this on their phone while doing two other things, or are they likely to give it a real seated five minutes? Phone-while-busy is single-page territory. Real seated minutes are multi-page territory. Ophelia's uncle in Tucson was phone-while-busy. The multi-page format was the wrong call for that audience even though the build was beautiful.

The five-step recipe, after you have picked the format

Below is the version that works for whichever format you have settled on. The first step is the format-pick (already done above); steps two through five are largely format-independent.

  1. Pick the cover. This is the highest-leverage decision after the format itself. A real photo of the recipient (or you and the recipient at a shared moment) is the strongest possible cover. A custom AI-generated cover, prompted with one specific detail about who they are, is second-best. A stock-template cover is a distant third and should be reserved for occasions where no photo exists and you cannot articulate anything specific enough to prompt the AI. The cover is what the email preview shows in the recipient's inbox. It is what they remember a month later. Spending one extra minute on this returns ten in delivered impact.
  2. Write the message inside, yourself, before you do anything else. For a solo card, this is the whole card. For a group card, your message is the first one posted, and it sets the standard every other signer reads before writing theirs. Two to four sentences. Name one real thing the recipient said, did, gave, or was. The word 'specific' is what carries the message; generic warmth lands as nothing.
  3. For group cards, post the link to the existing chat with one sentence of guidance. 'Hi all, signing a card for Marisol's last day, asking each of you to write a real two-line note rather than just "good luck".' The word 'specific' or 'real' in your invite text does about a third of the heavy lifting on the average signed quality across the rest of the card.
  4. Set the delivery moment. Use the recipient's time zone, never yours. The first thirty minutes after they typically wake up is the right window for most adults. On platforms that keep collecting signatures up to the delivery time, schedule early and let the late wave fill in; on platforms that lock at scheduling, schedule late and accept that the last-day signers will miss the window.
  5. Send. Or schedule, then send. Resist the urge to keep tweaking. The card you over-edited for ninety more minutes is no better than the card you finished an hour ago.

The AI cover step that most ecard platforms still cannot offer

The AI cover is the single most useful step that the older single-page ecard platforms still do not have natively, and it is a big part of why the format-pick matters less than it used to. You describe the recipient in one or two sentences, and the tool generates an illustration that fits. The stock-template balloon-and-cake covers are no longer the ceiling; the ceiling is now whatever you can describe about the specific person.

I made one last summer for a friend who teaches eighth-grade math and runs an ultramarathon habit on the side. The prompt was something like 'happy birthday to a math teacher who runs hundred-mile races and refuses to admit it is unusual'. The cover came back with a chalkboard equation winding into a trail through pines, which nobody on earth has on any other card, and which she immediately set as her phone wallpaper for a month. Reco's free online birthday ecards include this AI step natively across both the single-page and multi-page formats; most other free platforms do not, and the ones that do usually paywall it after the first try.

The caution is the same as before. Give the AI 'happy birthday' and you get a generic cake. Give it 'happy birthday to a marine biologist who loves Patti Smith and complains about the new wing of the Smithsonian' and you get something that no template library could have provided. Specificity in the prompt is what produces specificity in the output.

The mistakes I keep watching people make

A short list of the failure modes I have personally produced or watched friends produce, on cards I cared about and wish I had got right the first time.

  • Picking the multi-page format for a recipient who reads everything on a phone in two-second bursts.
  • Building the cover last, after spending forty minutes on background patterns and font choices that the recipient will not consciously notice.
  • Writing the inside message in the tone of an HR card when the recipient is your closest college friend, because the template's example text was an HR card and the tone bled in.
  • Sending the link to the group chat at 10pm Sunday with no context, when the same link sent Monday at 9am with one sentence of guidance would have produced twice the signed-message quality.
  • Scheduling the delivery for what feels like the recipient's morning without actually checking which time zone they will be in on the day; people travel.
  • Adding a music track on a card going to a recipient who reads everything on mute (which is most adults on a work computer or a quiet train).
  • Over-revising the card after it is already good enough; the eleventh tweak rarely improves a card and frequently makes it slightly worse by losing the looseness of the earlier draft.

None of these are catastrophic. All of them are easy to skip once you know to watch for them.

When the multi-page flip format actually earns its weight

I want to be specific about the cases where the multi-page format is the right call, because we have just spent the last three sections arguing the single-page case more aggressively than most product pages would. The multi-page works when one of these conditions is true.

The occasion is large and slow. A retirement after a thirty-year career. A milestone birthday where the recipient will sit down with coffee and actually read. A wedding card with multiple voices contributing. The pace of the format matches the pace of the moment.

The signers are few but each has something substantial to say. Three siblings to a parent, each with their own page and their own story to tell about the same person. Four close friends to one of their own at a marker year. The page-per-signer ratio gives each contribution the visual weight it should have, which the group-board layout does not.

The recipient is the type who keeps things. Some people open a card and then keep it for years; for them, the multi-page format reads as a small artifact rather than a quick note, and the flip animation adds to the felt sense of permanence. Others delete every email after reading; for them, the single-page format gets the same delivery without wasting effort on pages that will be deleted unread within the week. Knowing which type you are sending to is more useful than knowing every feature of every format. The piece on how to create a group ecard covers the group-board case at length if that turns out to be the right format for what you are building.

Turn it into a group card if the format calls for it

If the digital greeting card you are imagining has more than four or five voices on it, the group-card layout (board or multi-page-with-many-signers) is what you want. A group card online with multiple signatures handles the coordination without phone trees or paper cards passed around the office. One link goes to the chat the group already uses, each person writes their own line on their own time, and the card delivers itself at the moment you scheduled.

You can create a card online in a few minutes and the actual decisions (format, cover, delivery time) take five more. The signatures collect themselves while you do something else. For a workplace birthday going to a manager, birthday wishes for a boss has lines you can adapt for your own first signed message; for the broader 'what do I even write' question, what to write in a birthday card covers it without the boss-card formality.

If you are scheduling for a recipient in a different time zone than you, the piece on how to schedule a card delivery covers the time-zone trap I keep watching people fall into. The schedule field asks for a date and a time. The time zone is your problem, not the platform's.

One last thing, off-topic. Ophelia did, eventually, build a second card for her uncle, the same Tucson uncle, for his seventy-first birthday a year later. She built it as a single-page ecard with a photo of the two of them at his sixtieth-birthday cookout, which she had unearthed from an old laptop. No flip animation, no envelope transition, no AI cover; just the photo, a sentence under it, and his email. He texted her ninety seconds after delivery, on the morning of his birthday, while standing in the kitchen with her aunt making coffee. He said the photo was the best birthday present he had got that year, that he had forgotten the cookout entirely, and that he was going to print the card and put it on the fridge. She did not tell him she had spent eight minutes building it, four of those minutes finding the photo. The right format had been the single-page one the whole time. Most of the cards in your life that matter most will be that one.