Quick answer
The card carries the feeling and the essentials — who, what, when, and a way through. The page carries everything else. Put detail on the card and you will redesign it every time a detail changes.
What belongs on the card
A card is read in a few seconds, often as an image in a message thread. It should carry the names, the occasion, the date, the place in one line, and a clear route to reply. That is the whole job.
What belongs on the page
- The full schedule and any sub-events
- Directions, parking and public transport
- Accommodation options and any room block
- Dress code, gift preferences, children, accessibility
- The RSVP form itself, including meal choices and dietary notes
Why the split matters practically
Details change. A start time moves, a car park closes, a hotel block sells out. When those live on the page, you edit once and every guest who opens the link sees the current version — including the ones who saved the card months ago.
When they live on the card, you are reissuing an image and hoping nobody refers back to the old one.
Where the card gets used
A card is genuinely useful in three places: inside the invitation email, as a shareable link for group chats, and printed for the guests who would rather have paper. A card editor that exports a print-quality file and gives you a shareable web version covers all three from one design.
Keeping them consistent
The card and the page should look like the same event. Sharing a colour palette and typeface between them is enough — guests notice mismatch far more than they notice sophistication.
Do you need both?
For a small dinner, a page alone is fine. For anything with a design element — a wedding, a milestone birthday, a formal corporate evening — the card is what makes the invitation feel like an occasion rather than a calendar entry.