Multilingual RSVP
French + English on every site as core. Optional Arabic, Italian, Spanish. Guests pick their language; the entire site (including RSVP, registry, photobooth) follows. Most other wedding platforms ship one language.
Destination wedding website
A destination wedding website built for the world.
Multilingual RSVP (FR/EN core, AR/IT/ES extended). Multi-currency Stripe (8 currencies). Multi-event coordination. Public transport and accommodation pages. Time-zone-aware. Designed in Paris for destinations everywhere.
What destination weddings actually need
Eight features that aren't optional.
Multi-currency Stripe
EUR, USD, GBP, AED, JPY, CHF, AUD, CAD for the registry and honeymoon fund. Guests pay in your currency or their card's currency. Funds land directly in your bank via Stripe.
Multi-event RSVP
Welcome dinner Thursday. Boat trip Friday. Ceremony Saturday. Brunch Sunday. Each event has its own yes/no, dietary intake and plus-one logic. Guests confirm separately; you see per-event headcounts in real time.
Transport coordination
Public guest page (/transport) with airport pickup details, shuttle schedules, taxi recommendations and recommended arrival flights. Updates in real time as logistics evolve.
Accommodation hub
Public guest page (/stay) with recommended hotels, room block codes, alternative AirBnB suggestions and walking distance to the venue. Maps included.
Time-zone aware
Every event timestamp displays in the guest's local time zone on the wedding site, with the venue's local time as the reference. Guests in California always know what time their friends in Sydney are seeing.
Photobooth — works abroad
QR code in any country opens the photobooth instantly. No app to download (which matters at venues with poor wifi and guests with weak data plans). Live wall projects on the reception venue's screens.
AI design that respects culture
AI design generator that understands aesthetic by destination. "Tuscany golden hour" generates a different palette than "Marrakech riad". One-line vibe descriptions calibrated to the wedding's actual location.
How to start
Four steps from destination idea to launched site.
01
Pick a template + destination
All 36 editorial templates work for destination weddings — many are designed with locations in mind (Mediterranean, Parisian, coastal, Japanese garden, Moroccan riad). Or use AI to generate a design from a one-line vibe ("Tuscany golden hour", "Cap Ferret in October").
02
Configure languages + currency
Toggle French + English by default; add Arabic / Italian / Spanish if your guests need them. Pick your default currency (EUR / USD / GBP / etc). All RSVP forms, registry pages and photobooth flows respect the selection automatically.
03
Build the transport + accommodation pages
Drop the airport, the shuttle schedule, the hotel block codes, recommended AirBnBs. The public /transport and /stay pages on your wedding site update live. Guests bookmark them and stop emailing you.
04
Send digital invitations early
Destination guests need 6+ months to book affordable flights. Digital save-the-dates go out 10-11 months ahead. Formal invitations 6 months ahead. Email + SMS supported; each guest gets a unique personalized link.
Frequently asked
Quick answers about destination wedding websites.
What is a destination wedding website and what does it need?
A destination wedding website handles the additional logistical complexity of guests traveling internationally: multilingual flows (so guests in different countries can use the site in their language), multi-currency payments (for international honeymoon fund and registry contributions), multi-event RSVP (since destination weddings typically span 3-4 events over multiple days), public transport and accommodation pages (since guests need flight, shuttle and hotel information), and time-zone-aware display of every event.
Which wedding website builder is best for a destination wedding?
Look for: (1) genuine multilingual support — not just "Google Translate this page" but native RSVP and registry flows in multiple languages, (2) multi-currency Stripe — guests in different countries gift in their currency, (3) multi-event RSVP — not just one yes/no, (4) public transport + accommodation pages built in. e-invitation wedding ships all four. The Knot, Zola and Withjoy are US-centric — most lack one or more of these.
How many languages should a destination wedding website support?
At minimum, the languages of your two largest guest groups. For a French-American destination wedding, that's French + English. For a Lebanese-Italian wedding, Arabic + Italian (often with English as a backup for international friends). Three languages is the practical upper limit — beyond that, the UX gets cluttered.
How early should I send a destination wedding save-the-date?
10-11 months ahead. Destination guests need 6+ months to book affordable flights, request time off work, and coordinate international travel. A digital save-the-date sent 10-11 months ahead lets them block calendars early; a formal invitation 6 months ahead confirms attendance.
How do I handle currency for international honeymoon fund contributions?
Use a wedding platform with multi-currency Stripe checkout. Guests in different countries can contribute in their card's currency; the conversion happens at Stripe's standard rate (~0.5% above mid-market). e-invitation wedding supports EUR, USD, GBP, AED, JPY, CHF, AUD, CAD. Most US-centric wedding platforms only support USD, which costs international guests 2-4% in unfavorable conversions.
What public pages should a destination wedding website have?
At minimum: (1) main wedding site with the schedule, (2) /transport — airport, shuttle, taxi, recommended flights, (3) /stay — recommended hotels with discount codes, AirBnB suggestions, (4) /rsvp — multi-event RSVP form, (5) /honeymoon (if running a honeymoon fund), (6) /photobooth (during and after the wedding). All public, all accessible by URL share.
How do I handle dietary restrictions across international cuisines?
Use a per-guest dietary intake on RSVP that includes both standard categories (vegetarian, vegan, gluten-free, halal, kosher) and a free-text allergy field. The platform should aggregate across all guests and produce a chef-ready dietary sheet for the caterer in your destination — this saves a critical translation step when working with non-English-speaking catering teams.
Is destination wedding planning more expensive than local?
Sometimes yes, sometimes no. Destination weddings in Tuscany or the Côte d'Azur can cost 40-80% more than local equivalents. But destination weddings in Lisbon, Mexico, Greece or Croatia can be 20-40% cheaper than New York or London. The guest list self-trims (some guests can't travel), which saves linear costs on catering, drinks and stationery.
What about marriage license — do I get married legally at the destination?
Usually no. Most couples have the legal civil ceremony at home a few weeks before, then the symbolic ceremony at the destination. This avoids local marriage license complexity (many countries require residency periods of 30-90 days). Check with your destination's consulate and your home jurisdiction.
Can the wedding planner I hire access the destination wedding website?
Yes, via the Wedding Planner role. Grants full Management visibility (budget, vendors, transport, accommodation, day-of timeline) without billing access. Critical for destination weddings where you can't be on-site to handle logistics in the destination country.