Minimum nights on Airbnb: what I tested across five properties and why I keep changing my answer

The minimum nights setting is one of those Airbnb controls that looks simple and isn't. You can set a single minimum for your whole calendar, or different minimums for different seasons, or gap-fill rules that let 1-night stays fill orphan gaps even if your general minimum is 3. I've been adjusting these settings across five properties for three years and I've changed my mind about the right answer roughly six times.

Here's what I actually found, with specific numbers.

What the settings actually do

Airbnb lets you set:

• A global minimum stay (applies to all dates unless overridden)
• Seasonal minimum stays (you define date ranges with different minimums)
• A "prepare for guests" gap setting, which can differ from your minimum
• A gap-fill minimum (a shorter minimum that auto-applies to orphan gaps shorter than your standard minimum)

The gap-fill setting is the one most hosts I've talked to either don't know about or haven't used correctly. If your standard minimum is 3 nights but you have a 2-night gap between bookings, Airbnb won't show those dates to guests searching for 3-night stays — so the gap sits empty. Setting a gap-fill minimum of 1 or 2 nights lets Airbnb show those dates to shorter-stay guests. It's not automatic; you have to set it.

My Edinburgh experiment: going from 2 to 3 nights

In September 2024, I changed my Edinburgh Old Town flat from a 2-night minimum to a 3-night minimum. My reasoning: shorter stays meant higher turnover costs, more cleaner availability pressure, and more admin per booking. If I could attract longer-staying guests and drop turnover frequency, the maths should work even at similar or slightly lower occupancy.

For the first month, it worked. October 2024 against October 2023: revenue up 12%, occupancy down from 81% to 74%, but the per-booking cost was lower and the per-night revenue was slightly higher because I was occasionally filling with guests who'd pay a 3-night price even on a Thursday-to-Sunday where I'd previously have done a two-nighter Thursday-Saturday and another Friday-Sunday.

Then November happened. Edinburgh in November isn't the same as Edinburgh in October. Demand drops, the guest mix shifts towards business travellers and people visiting family — shorter-stay reasons rather than tourism. My 3-night minimum was filtering out a significant chunk of that guest pool. Occupancy dropped to 58% against 71% the November before. Revenue down 9% year-on-year.

I changed it back to 2 nights in late November and set a seasonal rule: 3-night minimum from April through October, 2-night minimum November through March. That combination has held since.

Why the season matters more than the number

Tourist-driven demand and personal-travel demand behave completely differently with respect to stay length. Edinburgh's tourist season (late spring through early autumn, plus Hogmanay) attracts guests who've planned a specific trip — they're often flexible on dates and willing to book 3 or 4 nights because the city is the destination. November through March, you're serving a much higher proportion of guests with a fixed reason to be in Edinburgh — a work meeting, a family visit, a specific event. They need Tuesday night. They don't need to extend it to fit a 3-night minimum.

Applying the same minimum year-round ignores this entirely and you'll end up optimising for one type of guest at the cost of the other.

Brighton: a completely different answer

My Brighton flat I run on a 2-night minimum year-round, and I've tried 3-night twice and reversed it both times. Brighton is different from Edinburgh: it's a short-break destination for London guests who are specifically doing weekend trips. The 1-hour train journey means a lot of demand is Friday-to-Sunday 2-night stays, and a 3-night minimum in Brighton means losing a disproportionate amount of demand because the natural trip length for most of my guests is exactly 2 nights.

The one exception: bank holiday weekends in summer. For those I temporarily raise the minimum to 3 nights — not through the seasonal setting, but by manually adjusting specific dates. Easter weekend, Late May bank holiday, Late August bank holiday. On those weekends, 3-night demand is strong enough that it's worth excluding the short-stay guests. The rest of the year, 2-night is the right answer for Brighton specifically.

The Lake District cottage: 4-night minimum in summer

The cottage is a different situation again. It's a 90-minute drive from the nearest major city and the turnover logistics — cleaner travel, linen changeover, supply restocking — make very short stays genuinely uneconomic. A 2-night stay at the cottage has nearly the same operational cost as a 5-night stay, because the cleaner drives 40 minutes each way and I'm restocking a rural property that isn't near an Amazon warehouse.

So: 4-night minimum from April through September, 3-night minimum October through March. This has dropped my booking count but the revenue per booking and the operational margin are both better. I was doing 18–22 bookings a year at the cottage with a 2-night minimum; I'm now doing 13–16 but each one is meaningfully longer and the cleaner isn't doing a 3-hour round trip for a couple who needed somewhere to sleep Friday night.

Orphan gaps: my actual gap-fill rule

Gap-fill minimums deserve more attention than they get. Currently I run:

• Edinburgh flat: global minimum 2 nights (summer: 3 nights). Gap-fill minimum 1 night for gaps of 2 nights or less.
• Brighton flat: global minimum 2 nights. Gap-fill minimum 1 night for 1-night gaps only.
• Lake District cottage: global minimum 3–4 nights. No gap-fill — a 1 or 2 night orphan gap at the cottage is better left empty than triggered by a guest who needs a full turnover for a 1-night stay.

The gap-fill 1-night rule for Edinburgh has filled about eight gaps in the past year that would otherwise have sat empty. At an average of £110 per night, that's roughly £880 in revenue I wouldn't have had without the setting.

What I'd check first if you haven't looked at this in a while

Pull your last 12 months of bookings. Count the number of gaps of 1 or 2 nights that sat between bookings and didn't fill. Multiply by your average nightly rate. That's approximately what an improperly configured gap-fill minimum is costing you per year.

Then look at your booking length distribution. What proportion of your bookings are 1 night? 2 nights? 4+ nights? If 60% of your bookings are 2-night stays and you've set a 3-night minimum, you're filtering out the majority of your natural guest pool and relying on demand being high enough to compensate. Sometimes it is. Often it isn't.

The right answer varies by property, by location, and by season. Which is annoying, but it's also the reason spending two hours getting this right will probably add more to annual revenue than another price optimisation tool.