AirCover Stops at the Airbnb Booking: What Covers a Direct Booking in 2026

TL;DR: the number is the marketing, the boundary is the product

Two figures do the work on Airbnb's AirCover page. One is $3M. The other is $1M. Both are real and both are quoted verbatim above. Neither tells you when they apply.

That is the whole problem. A coverage amount is a ceiling. A coverage boundary is a door. Hosts read the ceiling and assume the door is always open. It is not.

The door here is the booking channel. Protection follows the reservation, and the reservation has to be an Airbnb reservation. Most hosts learn this in the worst possible order. They build a direct booking channel because the fees are better. They take a booking. Something breaks. Then they find out which policy was listening.

What Airbnb's own page says, and what it does not

We read the AirCover for Hosts page directly rather than repeating a summary of it. Two things stood out.

The first is that the coverage amounts are stated plainly. $3M damage protection. $1M liability insurance for guest injury or property damage. Those are the page's own words.

The second is that the same page carries no exclusion list. It offers a link. The text points you to complete details on how AirCover protects you "and any exclusions that apply." The exclusions live behind that link, not on the page that carries the numbers.

That is a design choice, and it is worth naming. The figure is on the surface. The conditions are one click deeper. A host who reads only the surface leaves with two numbers and no boundaries. This is the same shape as any results claim that publishes a total and defers the method.

We are not calling that improper. Every insurer summarises. But it does mean the headline is not a description of your coverage. It is a description of a ceiling.

Why the platform boundary is the one that costs money

Consider how the protection is triggered. A guest books. The booking creates a record. The record has an ID, a payment, a check in date, and a check out date. Every part of a claim hangs off that record.

Now take that record away. Your guest booked on your own site. They paid through your own processor. There is no Airbnb reservation ID. There is no Airbnb payment. There is no Airbnb message thread holding the evidence.

The claim has nothing to attach to. This is not a technicality that a sympathetic agent waives. The product is scoped to the platform's own bookings.

The awkward part is that direct booking is good advice. Lower fees, owned guest relationships, and a channel nobody can suspend are all real benefits. We have written about building that channel in our direct booking website guide. The advice stands. What changes is that the moment the channel works, part of your protection stops travelling with it.

Where a direct booking is actually exposed

The table below sets out the surfaces a host usually assumes are covered, and which of them the platform product was written for. Treat the right column as the question to take to your own broker, not as a verdict on your policy.

Two rows repeat across both columns. Structure and lost income are not platform protection on either channel. Vendor analyses published in 2026 make the same point about structural cover and loss of rental income. Those are the two most common surprises, and neither is about direct booking at all. They are about what a booking level product was ever meant to do.

The 2026 evidence rule that changed how claims are built

One change this year is worth knowing whichever channel you sell through. Airbnb updated its terms effective 20 April 2026. Multiple 2026 vendor analyses describe the same two effects. Evidence standards for claims tightened. And AI generated, AI enhanced, or upscaled photographs are no longer acceptable as claim evidence.

Read that second one twice. Many hosts now run listing photos through enhancement tools by habit. The same habit applied to a damage photograph can now void the evidence.

The practical rule is to keep two separate photo pipelines. One is for marketing, where enhancement is fine. One is for evidence, where the file must be the original camera output and nothing else. We cover the evidence timing side in our note on the terms update.

A direct booking has no platform evidence standard at all. That sounds like freedom. It is not. Your own insurer sets the standard instead, and insurers are rarely more relaxed about photographs than platforms are.

A checklist for finding your own gap

Work through these in order. Each one closes a different assumption.

1. Count your channels. List every way a guest can pay you. Airbnb, other platforms, your own site, and a bank transfer from a repeat guest all count.
2. Mark which are platform bookings. Only one of those channels carries platform protection. Circle the rest. That set is your exposure.
3. Read your own policy for the word rental. A standard homeowner policy often excludes commercial or short term letting. If the word appears in an exclusion, assume you are not covered while hosting.
4. Ask your broker one question in writing. Ask whether a paying guest who booked outside a platform is covered. Get the answer in writing, not on a call.
5. Check the structure separately. Ask who pays if the building itself is damaged. Booking level protection is not the answer on any channel.
6. Check loss of income separately. Ask what pays while the unit cannot be let.
7. Split your photo pipeline. Keep original files for evidence. Keep enhanced files for listings. Never let the two mix.

None of these require a lawyer. They require writing down what you already half know, and then asking one person who is paid to answer.

Mistakes and risks that leave a host uncovered

The first risk is reading a ceiling as a guarantee. $3M is a limit, not a promise that any given event is inside the policy.

The second risk is assuming coverage travels with the property. It does not. It travels with the booking. Two guests in the same room in the same week can sit on different sides of the line.

The third risk is the homeowner policy nobody re read. Many hosts started with a normal residential policy and never revisited it after the first guest. That policy may exclude the activity entirely.

The fourth risk is treating a platform product as a substitute for a policy. It is a supplement. Vendor analyses through 2026 consistently describe hosts combining platform protection with a dedicated short term rental policy rather than choosing between them. Our insurance comparison walks the options.

The fifth risk is the quiet one. It is enhancing a damage photo out of habit. That single click can turn valid evidence into inadmissible evidence.

Comparing what each layer is actually for

Hosts often ask which product to buy. That is the wrong question. These are layers, not alternatives. The table sorts them by what they are built to answer.

Read the blind column, not the built column. Every host we have seen surprised by a claim was surprised by something in the right hand column. A comparison of two named carriers sits in our carrier comparison.

What this page cannot tell you

It cannot tell you whether you are covered. Only your policy document and your broker can do that, and both are specific to you, your property, and your country.

It cannot list Airbnb's exclusions authoritatively. The page carrying the coverage figures does not carry them, and we are not going to invent a list to fill the gap. The exclusion detail sits behind the link that page provides, and that is where it should be read.

It cannot promise that a dedicated policy covers everything either. A policy bought without reading the exclusions reproduces the same mistake one layer down.

What it can do is name the boundary that the headline figure hides, and give you a way to test your own position in an afternoon.

Summary and what to do next

The headline says $3M and $1M. Those figures are real and they are quoted from Airbnb's own page. They are also ceilings on a product scoped to bookings made on that platform.

If every booking you take is an Airbnb booking, the gap discussed here is narrow. If you have built a direct channel, or you sell on more than one platform, the gap is as wide as the share of revenue that arrives outside Airbnb.

The next step is small. Work out what percentage of last year's revenue came from outside the platform. That single number is the size of your exposure. Take it to your broker with the checklist above and ask the one written question.

One habit is worth building today, before any of this is urgent. Keep a single page that lists every channel you sell through, the protection attached to each, and the date you last checked it. Review it once a year and after any change to how you take bookings. Most gaps described here open quietly. A host adds a direct site, or turns on a second marketplace, and the protection map silently stops matching the business. A page that is reviewed on a schedule catches that drift. A memory does not. Our fuller breakdown of what the platform product covers sits in the AirCover guide. Read it next if you want the platform side in depth before you call anyone.

One broken table, walked through both channels

Abstractions hide the gap. A worked case shows it. Take one event and run it down two paths.

The event is the same in both. A guest stays three nights. A dining table is left with a deep gouge across the top. The cleaner photographs it at eleven in the morning. Replacement is several hundred dollars. Nothing else in the property is touched.

Path one, the guest booked on Airbnb. There is a reservation ID. There is a message thread. There is a checkout timestamp. The claim attaches to all three. The host files inside the platform, submits the original photographs, and the process runs against the platform's own evidence standard. Whether it pays is a separate question. The point is that a route exists and every piece of evidence has somewhere to sit.

Path two, the guest booked on the host's own site. The stay was identical. The damage is identical. The photograph is identical. What is missing is the record. There is no platform reservation, so there is no platform claim to open. The host is now filing against their own policy, if their own policy covers paying guests at all.

Notice what did not change. Not the guest, not the property, not the damage, not the evidence. Only the channel changed. That is the entire lesson of this page in one paragraph.

Most hosts discover this in path two. They have run path one for years and formed a mental model where the property is covered. The model was never wrong on Airbnb. It was just never about the property.

How this works when you sell on more than one platform

Very few serious hosts sell on one channel now. A typical portfolio touches Airbnb, at least one other marketplace, and a direct site. Each channel carries its own protection scheme, or none.

The mistake is to assume the schemes are equivalent. They are not. They differ in what they cover, in the ceiling, in the evidence they accept, and in the window during which a claim can be opened. Two platforms can look similar in marketing and behave differently in a claim.

So the useful exercise is not to learn one scheme well. It is to build a single sheet with one row per channel. Record four things for each. What the ceiling is. What triggers a claim. How long you have to report. What evidence is accepted.

Once that sheet exists, one thing becomes obvious. The weakest row sets your real protection, because a guest chooses the channel, not you. You cannot steer damage toward the channel with the better scheme.

The sheet also settles an argument hosts have with themselves. Whether to keep pushing direct bookings. The answer does not change. Direct booking is still the better economics. It just moves a cost from the fee line to the insurance line, and that cost should be priced deliberately rather than discovered later.

What reasonable care means in practice

The 2026 terms update brought a reasonable care expectation alongside the tighter evidence rules. That phrase does real work in a claim, and it is worth understanding before you need it.

Reasonable care is a standard about your conduct, not the guest's. It asks whether an ordinary careful operator would have done what you did. It is assessed after the event, by someone who was not there, from the records you kept.

That last clause is the operational part. Your conduct is only visible through your records. A host who screens guests, states house rules, documents the property condition between stays, and responds to problems promptly has a record of care. A host who does all the same things and writes none of it down has the care and not the record.

Three habits carry most of the weight. Photograph the property in a consistent set between stays, so a before and after pair always exists. Keep guest communication on a channel you can export. Note the time you became aware of a problem, because timing questions come up in nearly every claim.

None of that is insurance advice. It is record keeping. But a claim is decided on records, and hosts routinely lose on the records rather than on the facts.

Deposits, screening, and where they actually sit

Hosts often reach for a damage deposit as the answer to this whole problem. A deposit is useful. It is not an answer.

A deposit is a floor. It recovers small amounts quickly and it changes guest behaviour, which is worth more than the recovery. Its ceiling is low by design, because a deposit high enough to cover a serious event would suppress bookings.

Screening tools sit in the same category. They reduce the probability of an event. They do nothing about the size of one. A portfolio protected only by screening is protected against the common case and exposed to the expensive one.

The layering that works runs in one direction. Screening lowers frequency. Deposits absorb the small tail. A policy absorbs the large tail. Platform protection covers a specific slice of the middle on a specific channel. Remove any layer and the ones beside it do not stretch to cover the gap.

Where hosts go wrong is treating these as a menu to pick from. They are a stack. The question is never which one. It is which layer is currently missing, and what the largest event that layer was supposed to absorb would cost you.

How to phrase the question so a broker can answer it

Most hosts get a vague answer because they ask a vague question. "Am I covered for Airbnb" invites a yes. It is the wrong question in two ways. It names one channel, and it asks about a platform rather than an activity.

Ask about the activity instead. The activity is letting a property to paying strangers for short periods, arranged through several channels, some of which you control.

Four questions get useful answers. Does this policy cover paying guests who booked outside a platform? Does it cover damage to the structure, and up to what limit? Does it pay lost rental income while the property cannot be let, and for how long? What must I do at the time of an incident for a claim to stand?

Ask all four in one email. Email matters. A written answer is a record you can produce later, and it forces precision that a phone call does not.

If an answer arrives with a condition attached, write the condition down beside the question. The conditions are the real policy. The headline is a summary of the conditions, in the same way that $3M is a summary of a document you have not read yet.

Why the answer differs by country

Everything above describes a structure rather than a jurisdiction. The structure holds broadly. The specifics do not travel.

Insurance is regulated nationally. Product names, what a standard residential policy excludes, whether a short term let is treated as a commercial activity, and which carriers will write the risk all vary. A guide written for one market can be confidently wrong in another.

Australia is the clearest example in our own traffic. Hosts there arrive with different questions because the strata and building rules interact with cover in ways that have no direct equivalent elsewhere. We keep that material separate for exactly this reason.

So take the structure from this page and the specifics from your own market. The structure is that protection follows the booking, that structural damage and lost income sit outside booking level products, and that records decide claims. Those three hold wherever you host. The names and the limits do not.