Multilingual RSVP
English, French and Arabic, with right-to-left layout for Arabic. A guest picks their language from a switcher and the whole site follows: sections, RSVP, registry, photobooth.
Destination wedding website
RSVP in English, French and Arabic. Registry prices in the currency you choose. Multi-event coordination, public transport and accommodation pages, and dates that mean the same day wherever your guest reads them. Built for couples worldwide.
What destination weddings actually need
English, French and Arabic, with right-to-left layout for Arabic. A guest picks their language from a switcher and the whole site follows: sections, RSVP, registry, photobooth.
Set your registry prices in whatever currency you like. Gifts are arranged between you and your guests, so there is no conversion and nothing taken out currency. Your guests arrange their gift with you directly.
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.
Public guest page (/transport) with airport pickup details, shuttle schedules, taxi recommendations and recommended arrival flights. Updates in real time as logistics evolve.
Public guest page (/stay) with recommended hotels, room block codes, alternative AirBnB suggestions and walking distance to the venue. Maps included.
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.
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.
A 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
01
Every template in the collection works for destination weddings, and many are designed with locations in mind (Mediterranean, Parisian, coastal, Japanese garden, Moroccan riad). Or generate a design from a one-line vibe ("Tuscany golden hour", "Cap Ferret in October").
02
Run the site in English, French or Arabic, and price your registry in the currency you choose. The RSVP forms, the registry and the photobooth all follow the language the guest picked.
03
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
Destination guests need 6+ months to book affordable flights. Digital save-the-dates go out 10-11 months ahead. Formal invitations 6 months ahead. Send on WhatsApp or by email; each guest gets a unique personalized link.
Frequently asked
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.
The languages of your two largest guest groups. For a French-American wedding that is French and English; for a Lebanese one, Arabic with English or French behind it. Those three are what the site speaks today, and two per wedding is usually right: past that a guest spends longer choosing than reading.
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.
Set your registry prices in the currency that makes sense for you, and let each guest arrange their gift with you directly, no conversion, no card fees, nothing taken out.
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.
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.
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.
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.
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.