How to sync Airbnb and Vrbo calendars (without double bookings)

A host in Dubrovnik lists one stone-cottage on both Airbnb and Vrbo to fill the shoulder season. Week one, a Vrbo guest books the last weekend in May. Nineteen hours later, before Vrbo's calendar block reaches Airbnb, an Airbnb guest books the same nights. Now two families have a confirmed reservation for one cottage, and you're the one who has to cancel — eat the penalty, lose the Superhost progress, and write the apology. That gap is the whole problem. Sync the two calendars correctly and it closes.

This guide walks through both ways to connect Airbnb and Vrbo: the free manual iCal method and the channel-manager method. You'll get the exact steps, a way to confirm the link is actually live, a plan for the dangerous first few hours, and a troubleshooting list for when a feed goes stale.

Why Airbnb and Vrbo calendars drift apart

Airbnb and Vrbo don't talk to each other by default. Each platform keeps its own calendar, and a booking on one is invisible to the other until you build a bridge between them. The cheapest bridge is iCal — a plain text feed each platform publishes at a private URL, listing every blocked date.

The catch is timing. iCal isn't live. Each platform re-reads the other's feed on a schedule — Airbnb refreshes imported calendars roughly every couple of hours, and Vrbo on a similar cadence. So a new Vrbo booking sits unseen by Airbnb until the next poll fires. That delay is the window where double bookings happen, and it's exactly why the iCal sync method needs the safeguards further down this page. If you want the full anatomy of how these collisions happen, our guide on how to avoid double bookings breaks down each failure mode.

How do you sync Airbnb and Vrbo calendars?

You connect them by exporting each platform's iCal link and importing it into the other, or by routing both through a channel manager that holds one master calendar. The manual route is free and works for a single listing. The channel-manager route costs money but syncs faster and scales past one unit.

Both methods are a two-way street. You import Vrbo's feed into Airbnb and Airbnb's feed into Vrbo — miss one direction and only half your bookings block.

Method 1: Manual iCal export and import

This is free and built into both platforms. You're copying two URLs and pasting each into the other.

On Airbnb, open the listing, go to the calendar, find Availability → Connect calendars → Export calendar, and copy the link. It ends in .ics. Airbnb documents the full flow on its calendar sync help page. Keep that URL private — anyone with it can read your blocked dates.

On Vrbo, open the property's calendar settings and look for the import/export section. Copy Vrbo's export link the same way.

Now cross-import. Back on Airbnb, in the same Connect calendars area choose to import a calendar, paste Vrbo's .ics URL, and give it a name like "Vrbo." On Vrbo, import Airbnb's link the same way. When both are in place, a block on either platform will eventually appear on the other.

Method 2: A channel manager or PMS

A channel manager connects to both platforms and keeps a single source-of-truth calendar. Book a night anywhere and the manager pushes the block out to every connected channel — often within a minute or two instead of hours.

The big difference is the connection type. Airbnb offers a direct API to approved partners, which is faster and richer than iCal — it carries pricing and reservation details, not just blocked dates. A property management system that holds Airbnb API access can close the sync gap to seconds. Vrbo also supports a partner connection beyond plain iCal. The trade-off is cost and setup: you're adding a tool and a monthly bill in exchange for a tighter, hands-off sync.

Manual iCal vs channel manager: which should you use?

A one-listing host can run on free iCal if they keep a buffer; a host with two or more units, or one who sells out fast, needs the speed a channel manager buys. Here's the honest split.

If you run a single unit and don't sell out months ahead, manual iCal plus a minimum-stay buffer is fine. The moment you add a second listing or start filling the calendar weeks out, the refresh gap stops being a nuisance and starts being a cancellation waiting to happen.

How do you verify the calendar link actually worked?

Block a test date on one platform and watch for it to appear on the other within the expected window. Don't assume the import took just because the URL pasted without an error — confirm it with a live block.

Run this checklist after connecting:

• Block a single future date on Vrbo (pick something months out so no real guest is affected).
• Wait through one refresh cycle — give it a few hours for iCal, a few minutes for a channel manager.
• Open Airbnb's calendar and confirm that date now shows as blocked.
• Repeat in reverse: block a date on Airbnb, confirm it lands on Vrbo.
• Unblock both test dates once you've confirmed both directions work.
• Paste each .ics URL into our free iCal feed checker to confirm the feed is valid, reachable, and not throwing duplicate or malformed events.

That last step catches the silent failures — a feed that returns an error, a malformed event, or a stale timestamp — before they cause a real collision.

What about the gap before sync goes live?

Treat the first 24 hours after connecting as a manual-watch period, because the cross-imports may not have completed a full cycle yet and an old booking on one platform might not have reached the other. Don't trust the automation until you've seen a test block cross both ways.

During that window, do two things. First, manually re-check any existing reservations — a Vrbo booking made yesterday may not yet block Airbnb. Second, set a short minimum-stay or an advance-notice buffer so a same-day double booking can't sneak through while feeds settle. We've seen two-property hosts in Split skip this and lose a weekend to a collision — the cancellation took an hour, but the dinged review and the Superhost reset took months to recover. A one-day buffer would have prevented all of it.

Even after sync is stable, the refresh gap never fully disappears on plain iCal. A booking that lands on Vrbo at 2 p.m. won't block Airbnb until the next poll. The narrower that gap, the safer you are — which is the entire argument for an API-level connection if you sell out fast.

Troubleshooting stale or broken feeds

When a synced calendar stops updating, the cause is almost always one of a handful of things. Work through them in order.

The feed returns an error. If a platform can't fetch the other's .ics URL, the import silently stops updating. Re-copy the export link — platforms occasionally rotate these URLs — and re-import it. Run the link through the iCal feed checker first to see whether it even resolves.

Only one direction syncs. This is the most common mistake. You imported Vrbo into Airbnb but forgot to import Airbnb into Vrbo. Bookings from the un-imported side won't block the other. Confirm both imports exist.

Dates appear late or not at all. That's the refresh cadence doing its job slowly, not a bug. iCal polls on a schedule; there's no "sync now" button on most platforms. If late blocks keep causing near-misses, that's your signal to move to a faster connection.

Duplicate or ghost blocks. If the same dates show up twice, or blocked dates linger after a cancellation, the feed may carry duplicate UIDs or stale events. The checker flags duplicate UIDs and overlapping events directly, which tells you whether the problem is the feed itself or the import.

Everything looks connected but a double booking still happened. Check the timestamps. If both bookings landed inside one refresh window, no iCal setup could have caught it — the two platforms simply hadn't talked yet. That's the structural limit of iCal, and the only fix is a faster sync layer.