Ask ten STR operators what their liability limit is, and most will be able to tell you, $500,000, $1 million, sometimes $2 million. Ask them how they arrived at that number, and the answer is almost always some version of "that's what the policy came with" or "that seemed like a reasonable number."
Reasonable compared to what, though? A liability limit isn't a number that exists in isolation. It's a number that exists in relation to a few specific things: the severity of claims your property could plausibly generate, the assets you have that a judgment could reach beyond your policy limit, and, for operators with more than one property, how your limit is structured across a portfolio.
Most operators have never walked through that relationship. This article is that walkthrough.
What "Limit" Actually Means
Before getting into how much is enough, it's worth being precise about what a liability limit actually describes, because the terminology gets used loosely and the differences matter.
Per-occurrence limit. This is the maximum amount the policy will pay for a single claim, one incident, one injured party, one lawsuit. If your policy has a $1 million per-occurrence limit and a guest's injury claim settles for $750,000 plus $100,000 in defense costs (assuming defense is inside the limit, which is a separate question addressed below), the policy pays $850,000 and you're within limits with $150,000 of headroom remaining for that claim.
Aggregate limit. This is the maximum the policy will pay across all claims during the policy period, typically one year. For a single-property operator, the aggregate limit rarely matters in practice, because it would take multiple severe claims in the same year to approach it. For operators with multiple properties under one policy, the aggregate limit matters quite a bit, and we'll come back to this.
Defense costs inside vs. outside limits. This is one of the most consequential and least understood differences in liability coverage. Some policies pay legal defense costs as part of the liability limit, meaning a $1 million limit might be reduced to $850,000 of actual injury settlement coverage after $150,000 in legal fees. Other policies pay defense costs separately, outside the limit, meaning the full $1 million remains available for the settlement regardless of how much was spent on defense. For a property with meaningful litigation exposure, this difference can be worth hundreds of thousands of dollars in a serious claim. It is also one of the easiest things to overlook, because it doesn't show up as a number on the declarations page, it's a clause buried in the policy language.
Where $1 Million Comes From, and Why It's a Starting Point, Not an Answer
A $1 million per-occurrence liability limit has become something close to a default standard in STR-specific insurance, and for good reason. It's a level that comfortably covers the overwhelming majority of premises liability claims an STR property generates. Looking across the incident reports in our case file series: a hot tub slip-and-fall settled at roughly $65,000. A pool near-drowning settled at $56,000. A dog bite, a guest injury from a falling object, a cabin fire liability component, none of these, even at the higher end of severity, approached $1 million.
For a large share of STR operators, a single property, moderate guest volume, no unusual amenities, in a market with a typical litigation environment, $1 million per occurrence is a defensible number. It is not undersized for the realistic claim severity those operators are likely to face.
But "$1 million is often enough" and "$1 million is enough for you" are different statements, and the gap between them is filled by three questions that have nothing to do with insurance products and everything to do with your specific situation.
Question One: What Does Your Property Actually Expose You To?
Claim severity is not uniform across STR properties. It scales with a few specific, identifiable factors, and a property with several of these factors present is operating in a meaningfully different risk tier than a property with none of them.
High-severity amenities. Pools, hot tubs, docks and waterfront access, elevated decks and balconies, fire pits, and any other feature where the worst-case injury scenario involves drowning, severe falls, burns, or traumatic injury rather than a sprained ankle. A property with a pool is not in the same risk tier as a property without one, regardless of how well-maintained the pool is, the ceiling on claim severity is simply higher when the underlying hazard is more severe.
Guest capacity. A two-bedroom property sleeping four and a six-bedroom property sleeping sixteen carry different exposure profiles, independent of anything else about the property. More guests per stay means more people interacting with every hazard on the property, more frequently, across more bookings per year. We have reviewed a trampoline injury claim that arose from a family reunion booking of fourteen people, exactly the kind of large-group booking that higher-capacity properties are marketed toward, and exactly the kind of booking where multiple children of different ages using the same amenity at the same time becomes likely rather than hypothetical.
Number of structures and outbuildings. A property with a guesthouse, a detached garage converted to additional sleeping space, a barn, or other secondary structures has more square footage where something can go wrong, and in some cases more complexity in how the policy treats each structure.
Litigation environment. This is the factor operators are least equipped to assess on their own, and it's real. Jury verdict patterns, the prevalence of attorney advertising for premises liability cases, and the general litigation climate vary meaningfully by state and even by county. A property in a market with a more aggressive plaintiff's bar and a history of larger premises liability verdicts carries a different severity ceiling than an identical property in a market where verdicts of that size are rare. This isn't something you can look up in five minutes, but it's something a broker who places STR coverage regularly in your specific market will have a working sense of, and it's a legitimate factor in deciding whether $1 million is a ceiling or a floor for your property.
None of these factors individually demands a specific number. Together, they describe whether your property sits closer to the middle of the STR risk distribution or out toward the tail, and the tail is where a $1 million limit starts to look thin rather than comfortable.
Question Two: What Happens Above the Limit?
This is the question that liability limit conversations most often skip entirely, and it's the one that actually determines how much coverage you need.
A liability policy limit is not a cap on your exposure. It's a cap on the insurance company's exposure. If a judgment or settlement exceeds your policy limit, the difference doesn't disappear, it becomes a personal financial obligation, and in the absence of other arrangements, it's an obligation that can reach your personal assets: savings, investment accounts, other real estate, and in some circumstances future income.
This reframes the liability limit question entirely. It's not "how much coverage do I need for this property" in isolation. It's "how much of my total personal financial picture do I need to protect from a judgment arising out of this property." For an operator with relatively modest personal assets beyond the property itself, the gap between a $1 million limit and a hypothetical $1.5 million judgment, while serious, may represent a recoverable financial setback. For an operator with substantial assets, other real estate, retirement accounts, a investment portfolio, a primary residence with significant equity, that same $500,000 gap represents a direct claim against assets that have nothing to do with the STR property where the incident occurred.
The common heuristic in personal risk management is that liability coverage should be considered in relation to net worth, not in relation to the value of any single asset. An operator whose total net worth, across all properties, accounts, and assets, is $400,000 has a fundamentally different risk calculus than an operator whose net worth is $4 million, even if both of them own STR properties of similar value and similar risk profile. The second operator has more to lose above any given limit, which means the second operator's "enough" is a larger number, independent of anything about the property itself.
This is the most important reframe in this entire article: liability limits protect your assets, not your property. The property has its own coverage for its own damage. The liability limit exists because of everything else you own.
Question Three: How Is Your Coverage Structured Across Multiple Properties?
For operators with a single property, the per-occurrence limit on that property's policy is the relevant number. For operators with multiple properties, and particularly for property managers responsible for a portfolio of properties owned by others, the structure gets more complicated, and the complications matter.
Aggregate limits across a portfolio. Some policies that cover multiple properties apply a single aggregate limit across the entire portfolio for the policy period, rather than a separate aggregate for each property. If a severe claim at one property consumes a substantial portion of that aggregate early in the policy year, the remaining properties in the portfolio have less coverage available to them for the rest of the year, not because anything happened at those properties, but because the shared aggregate has been drawn down. This is a structural feature worth understanding explicitly if you operate or manage more than one property under a single policy: ask directly whether the aggregate limit is per-property or shared across the portfolio, and what happens to coverage at unaffected properties if the shared aggregate is significantly impacted by a claim elsewhere.
Per-location vs. blanket limits. Related to the aggregate question is whether the per-occurrence limit itself applies separately to each location or is a blanket limit that could, in some policy structures, be affected by how claims are categorized. This is technical policy language, and it's exactly the kind of thing that should be confirmed explicitly with whoever places the coverage rather than assumed from the declarations page summary.
Property managers and owner-of-record questions. For property managers operating on behalf of property owners, there's an additional layer: whose policy responds first, how the management company's own liability exposure is covered separately from the property owner's, and whether the management agreement itself allocates risk in ways that affect what coverage each party needs to carry. This is a more involved conversation than a single-property operator's coverage review, and it's one of the areas where a portfolio-level insurance relationship, rather than a series of individual property policies, becomes operationally important.
Umbrella Policies: What They Do and the Exclusion That Changes Everything
An umbrella policy is excess liability coverage, it sits above one or more underlying policies and responds when a covered claim exceeds the underlying policy's limit. A $1 million umbrella sitting above a $1 million STR liability policy effectively gives you $2 million of coverage for a claim that the underlying policy covers but that exceeds its limit.
That phrase, "for a claim that the underlying policy covers", is the entire story, and it's worth dwelling on, because it's the source of one of the most consequential misunderstandings in this entire topic.
An umbrella policy generally does not create coverage independent of the underlying policy. If the underlying policy excludes a particular type of claim entirely, the umbrella typically does not step in to cover it just because the underlying policy didn't. The umbrella follows the underlying policy's coverage, it extends the limit, but it doesn't expand the scope.
This matters enormously for STR operators specifically, because of how personal umbrella policies are written. Most personal umbrella policies, the kind that sit above a homeowner's policy and an auto policy, marketed to individuals and families, contain exclusions for business activities. Operating a property as a short-term rental is, for insurance purposes, a business activity. An operator who has purchased a personal umbrella policy, assuming it provides an additional layer of protection over their STR operation, may find that the umbrella simply doesn't apply to STR-related claims at all, not because the limit is too low, but because the entire category is outside the umbrella's scope.
This is precisely what happens in claims of that kind. In one, the operator had purchased an additional $1 million in umbrella liability protection specifically because he understood hosting families with children carried elevated exposure. When the claim arose, the umbrella's own exclusion, written in materially similar language to the underlying policy's exclusion, meant it provided zero response. The extra limit he'd paid for was never in play, because the type of claim was excluded at both layers.
The practical implication: if you carry a personal umbrella policy and you operate an STR, the question to ask explicitly is whether the umbrella has been confirmed to extend over your rental activity, not whether you have an umbrella, but whether this umbrella, as written, responds to a claim arising from your STR operation. For many operators, the honest answer, once they ask, is no.
The Alternative: Excess Liability Written for the STR Itself
The solution isn't necessarily to abandon the idea of an umbrella, it's to make sure the excess layer is structured for the activity it needs to cover. Some STR-specific carriers and specialty markets offer excess liability or umbrella coverage written specifically to sit above an STR liability policy, following that policy's form rather than a personal umbrella's form. This is sometimes called a commercial umbrella or excess liability policy, and it's a different product from the personal umbrella most operators are familiar with.
For an operator whose risk assessment, based on the factors discussed above, amenities, capacity, litigation environment, and personal asset exposure, points toward needing more than the base $1 million, this is the product category to ask about. The conversation with a broker should be specific: "I have a $1 million STR liability policy. I'd like an additional $1-2 million in excess coverage that explicitly follows this policy's form and responds to the same categories of claims. What's available, and what does it cost?"
Pricing for excess liability layers above an underlying STR policy varies by market and by the specifics of the property, but as a general matter, excess layers are priced more efficiently than primary layers, the first $1 million of coverage costs more per dollar of protection than the second or third million, because the probability of a claim reaching into the excess layer at all is lower. For many operators whose risk assessment points toward needing $2-3 million in total protection, the incremental cost of the excess layer is modest relative to the base policy premium.
A Framework for Arriving at Your Number
Pulling this together into something usable: there is no formula that outputs a single correct number, but there is a sequence of questions that, worked through honestly, points toward a defensible range.
Start with your property's risk tier. Does it have high-severity amenities, pool, hot tub, waterfront, elevated structures? What's the guest capacity, and does the property attract large-group bookings? Is the litigation environment in your market one your broker has flagged as having a history of larger premises liability outcomes? A property with several of these factors present is operating closer to the tail of the claim severity distribution, and a base limit that would be comfortable for a lower-tier property starts to look thinner.
Then look at your personal exposure independent of the property. What is your total net worth, across all real estate, retirement accounts, investments, and other assets? The liability limit on this property exists, in part, to protect everything else you own from a judgment that exceeds it. An operator with significant personal assets beyond the STR property itself needs a higher limit than an operator whose net worth is concentrated almost entirely in the property, not because the property is riskier, but because there's more on the table above the limit.
Then, if you operate more than one property, understand your aggregate structure. Is the aggregate limit shared across your portfolio or separate per property? A shared aggregate that looks adequate on paper can be functionally inadequate if a single severe claim early in the policy year draws it down for every other property you operate.
Finally, confirm, explicitly, in writing if possible, whether any umbrella or excess coverage you carry actually extends to your STR activity. If you have a personal umbrella, ask the direct question about business activity exclusions. If the answer is that it doesn't extend, that's not a reason to assume you're stuck at the base limit, it's the starting point for a conversation about excess coverage written for the activity you actually have.
None of these four questions produces a number on its own. Together, they produce a range, and for most operators, working through them honestly for the first time is the first time they've thought about their liability limit as anything other than a default that came with the policy.
The Bottom Line
A $1 million per-occurrence liability limit is a reasonable starting point for a large share of STR operators, and for some operators it remains the right number after going through this analysis. For others, particularly those with high-severity amenities, larger guest capacities, meaningful personal assets beyond the property, or multi-property portfolios with shared aggregate limits, the analysis points toward something higher, often through an excess or umbrella layer written specifically to follow the STR policy.
The number itself matters less than the process of arriving at it. An operator who has gone through these four questions and landed on $1 million is in a fundamentally different position than an operator who has $1 million because that's what the application defaulted to, even if the number on the page is identical. One of them knows what that number is protecting and has confirmed it's the right amount. The other is hoping it's enough and has never had reason to find out otherwise.
Schedule a full audit with Threshold STR to walk through this analysis for your specific property and portfolio, or take the free five-minute Risk Score to see where your current coverage structure stands.
This article is prepared by Threshold STR for educational and operational guidance purposes. It does not constitute insurance, legal, or financial advice and is not a substitute for a professional insurance review. Liability limit needs vary based on individual circumstances. Before making coverage decisions, consult with a licensed insurance professional in your state.