top of page

Yachats vs Florence: Two Oregon Coast Towns, Two Years

Devil's Churn rocky inlet near Yachats, Oregon. Wikimedia: Yachats Basalt Devil's Churn.

Florence and Yachats sit roughly 25 miles apart on the Oregon coast, close enough that a buyer or host evaluating one often ends up weighing the other. That comparison is worth making honestly, because the two towns are genuinely different markets — different guest, different desk, different calendar, and this year, a different revenue picture entirely — not a bigger town and a smaller version of the same thing.


This post lays out that comparison directly: what each town actually offers, how their permit structures differ, and what the current data says about each one's revenue picture. Florence is already covered as its own market on this site, with its own dedicated content; this post exists specifically to help a reader weighing both make an informed, honest choice rather than defaulting to whichever town has more name recognition.


Neither town is objectively better. The right answer depends on what a specific buyer or host is actually optimizing for — and that answer changes depending on guest type, entry cost, and which permit desk a buyer can actually use. This post treats each factor separately rather than collapsing them into a single, oversimplified verdict. This is not legal advice.


Identity: dunes recreation vs. working-village quiet

Florence's identity centers on the Oregon Dunes National Recreation Area — sand dunes, ATV and dune-buggy recreation, a broader range of visitor activities built around that landscape. It draws a guest looking for an active, recreation-focused coastal trip, often in larger groups equipped for dune riding or beach recreation on a bigger scale.


Yachats's identity is nearly the opposite: a small, working village on Highway 101, built around Cape Perpetua's tide pools and old-growth trails, the 804 Trail's walkable coastal path, and a two-block downtown that reads as a genuine small community rather than a tourist destination built for volume. A guest choosing Yachats is often specifically choosing quiet and scale over the more active, larger-footprint experience Florence offers.


These are not competing versions of the same product. A property well-suited to a dune-recreation guest in Florence is not automatically well-suited to a tide-pooling, trail-walking guest in Yachats, and marketing one town's property using the other's identity — a mistake covered in more depth in this cluster's how-to-market post — misrepresents what a guest will actually experience.


Even the physical property types that tend to suit each town reflect this difference. A Florence property built around group capacity and proximity to dune access points serves its market well; a Yachats property built around a quiet reading nook, a good storm-view window, or walkable proximity to the 804 Trail serves its own market equally well but for an entirely different reason. Neither design approach transfers cleanly to the other town.


The permit desks: an open market vs. a hard cap

This is one of the most concrete, practical differences between the two towns, and it deserves attention beyond general market vibes. Yachats operates under a hard citywide cap of 125 vacation-rental licenses, administered by the City of Yachats under Municipal Code Chapter 4.08, with an active waitlist as of this report's research. A new Yachats short-term rental license is not simply available on demand — it requires joining a waitlist tied to a fixed cap.


Florence's regulatory structure is its own separate system, covered in that market's dedicated content on this site rather than restated here, and a buyer evaluating both towns should research Florence's specific permit requirements directly through Florence's own regulatory sources rather than assuming it mirrors Yachats's capped structure. The two towns should not be assumed to share a regulatory approach simply because they are both Oregon coast markets — verifying each town's actual permit desk independently is a necessary step regardless of which town a buyer ultimately chooses.


This difference matters beyond simple compliance. A capped, waitlisted market like Yachats structurally limits how much new competing supply can enter, which is part of what supports the town's relatively strong occupancy figures even as overall coastal supply grows. A buyer comparing the two towns purely on entry cost or revenue potential, without weighing how each town's regulatory structure shapes future competitive dynamics, is missing a meaningful part of the long-term picture.


This year's revenue picture: two different numbers, two different confidence levels

Yachats's most recent AirROI pull shows roughly $45,011 in typical annual revenue — a labeled annualization sitting a single table-row above this desk's $45,000 threshold, a genuinely knife-edge figure this year rather than a comfortable clearance. Two other sources for Yachats disagree meaningfully: AirDNA's MarketMinder shows roughly $43,100, and a third Edge/Teeco-style estimate runs near $68,000 — a spread worth taking seriously rather than averaging into a single misleading number.


Florence's own revenue figures are covered separately in that market's dedicated content and are not restated here, since presenting them secondhand in this comparison post risks the exact kind of stale or misapplied number this cluster works hard to avoid. A reader genuinely comparing the two towns' current revenue pictures should check each town's own dedicated market report directly for the most current figures, rather than relying on a summary embedded in a comparison post.


The broader point worth taking from this section isn't which town's number is bigger — it's that Yachats's number this year carries a specific kind of uncertainty (a knife-edge margin above a threshold) that a buyer should understand on its own terms, independent of how Florence's market happens to be performing. Treating Yachats's revenue picture as automatically comparable to, or a discount version of, Florence's misses the specific character of what's actually happening in each town's data this year.


Guest calendar: how each town's peak season actually behaves

Yachats posts the highest occupancy among Oregon-coast KEEP-tier markets this desk currently tracks — 45.2% on the AirROI pull — with August as the peak revenue month, June and September also strong, and January as the confirmed low point. That relatively high overall occupancy suggests Yachats holds guests through more of the calendar than a purely summer-driven coastal town, aided in part by genuine storm-watching demand in the winter months, covered in more depth in this cluster's shoulder-season post.


Florence's own seasonal pattern, tied more directly to dune-recreation activity, likely follows a different calendar logic — dune recreation tends to have its own weather and access-dependent patterns distinct from Yachats's tide-pooling and storm-watching calendar. A buyer weighing both towns for calendar-fit reasons, such as planning around personal use of a property during specific months, should research each town's actual seasonal pattern independently rather than assuming both towns share Yachats's specific monthly breakdown.


This distinction matters for a host planning any kind of hybrid personal-use-and-rental strategy across a calendar year as well. A host who owns or considers owning in both towns should map each one's actual peak and trough months separately rather than assuming they overlap, since a month that's ideal for personal use in one town might be that same town's most valuable rental month — while the other town's calendar could look completely different.


Who actually wins this comparison — it depends on the guest

For a buyer or host targeting a dune-recreation, larger-group, more active-vacation guest, Florence's established identity and infrastructure around that experience is likely the better fit — trying to force that guest profile into Yachats's quieter, smaller-scale offering would misrepresent both the property and the town.


For a buyer or host targeting a quieter, trail-and-tide-pool guest, or the storm-watching and walkable-village guest covered in this cluster's who-books post, Yachats is the better fit specifically because it offers something Florence's larger, more recreation-focused identity doesn't compete for. Neither town is the objectively "better investment" in the abstract — the right choice depends entirely on which guest a specific property and host are actually positioned to serve well.


A useful question for a buyer genuinely torn between the two: which town would you rather spend a week in yourself, and which guest experience can you describe in specific, honest detail without reaching for generic coastal-vacation language? A buyer who struggles to describe Yachats's appeal beyond "it's quiet" may not be the right host for that market, just as a buyer who can't speak specifically to dune recreation may not be well-suited to marketing a Florence property effectively.


What a buyer weighing both should actually do

The practical next step for someone genuinely deciding between the two towns is not to rely on a single comparison post like this one for a final decision, but to pull each town's own current, dedicated market report and regulatory research directly, confirm which permit desk applies to any specific property under consideration, and honestly assess which guest persona — dune-recreation Florence visitor or quiet-coastal Yachats visitor — the specific property and the buyer's own marketing capacity are actually suited to serve.


This is not legal or financial advice. A purchase decision between two markets this different in character should involve direct research into each town's current data and regulatory status, not a single blended comparison treated as the final word.


A note on distance and drive-market overlap

Because the two towns sit roughly 25 miles apart, there is genuine overlap in the broader regional visitor pool — a guest researching "central Oregon coast" options may realistically consider both towns before booking either one. This overlap is worth understanding for marketing purposes even though it doesn't change the underlying fact that the two towns serve meaningfully different guest intents once a booking decision is actually made.


A Yachats listing competing in broader regional search results may occasionally show up alongside Florence properties, which makes the town-specific merchandising covered throughout this cluster even more important — a guest comparing a dune-recreation Florence listing against a quiet Yachats cottage needs the listing copy itself to make clear which experience they're actually choosing, rather than relying on the guest to already know the difference between the two towns before they start browsing.


This is exactly the scenario where generic "Oregon coast" listing language does the most damage — in a head-to-head regional search, a specific, honest description of what Yachats offers is what actually wins the booking from a guest who might otherwise default to the more recognizable name.


Why this comparison exists as its own post rather than folded into the market report

This cluster's market report focuses specifically on Yachats's own numbers, deliberately avoiding blending in comparison data that could dilute the town's own knife-edge figure with a neighbor's different revenue picture. This vs-Florence post exists separately so that a genuine head-to-head comparison has room to be thorough without compromising the market report's focus on Yachats alone.


That separation reflects a broader principle worth stating plainly: comparing two markets honestly requires giving each one's own data room to stand on its own terms first, rather than immediately blending them together. A reader who wants Yachats's numbers should get Yachats's numbers, cleanly, without Florence's different revenue picture muddying the figure. A reader who wants the comparison gets it here, in a post built specifically for that purpose.


Related Reading

More Yachats vs Florence host reading on desks, calendars, and listing clarity.


Frequently Asked Questions

Is Yachats a cheaper or smaller version of Florence for short-term rental investment?

No — they're different markets with different guest identities, not a bigger town and a smaller version of the same thing. Florence centers on dune recreation; Yachats centers on quiet, tide pools, trails, and a working-village character. Comparing them as "which is the better deal" misses that they serve different guests.


Does Florence have the same vacation-rental license cap as Yachats?

This post does not restate Florence's specific regulatory structure, since it's covered in that market's own dedicated content. A buyer should verify Florence's actual permit requirements directly rather than assuming it shares Yachats's capped, waitlisted structure — the two towns should be researched independently.


Which town has higher short-term rental revenue, Yachats or Florence?

Yachats's current figure sits at roughly $45,011 on the primary AirROI pull, a knife-edge number this year. Florence's figures are covered in that market's own dedicated report and aren't restated secondhand here — check each town's current market report directly for an accurate, current comparison.


What kind of guest books Yachats instead of Florence?

Yachats attracts guests specifically seeking quiet, walkability, tide pooling near Cape Perpetua, and storm-watching — often guests who have deliberately chosen a smaller, calmer alternative to busier or more recreation-focused coastal towns rather than a dune-recreation, larger-group vacation guest.


Should I buy in Yachats or Florence if I want a property for dune recreation guests?

Florence's established identity and infrastructure around dune recreation makes it the more natural fit for that specific guest profile. Trying to market a Yachats property toward dune-recreation guests would misrepresent what the town actually offers.


Is Yachats's occupancy rate higher or lower than Florence's?

Yachats posts the highest occupancy among Oregon-coast KEEP-tier markets this desk currently tracks, at 45.2%. Florence's specific occupancy figure is covered in that market's own dedicated content and should be checked there directly for an accurate comparison.


Can I use Florence's regulatory information to plan a Yachats purchase, or vice versa?

No. Each town's permit desk, fee structure, and cap status are separate and should be researched independently. Assuming shared regulation because both are Oregon coast towns is a common and avoidable mistake.


Which town is the better investment, Yachats or Florence?

Neither is objectively better — the right choice depends on which guest a specific property and host are positioned to serve well, plus each town's current revenue and regulatory picture at the time of purchase. A dune-recreation-focused buyer likely fits Florence better; a quiet-coastal-focused buyer likely fits Yachats better.


How far apart are Yachats and Florence?

Roughly 25 miles, close enough that both towns are sometimes considered together by buyers scouting the central Oregon coast, but far enough apart in character and guest identity that they shouldn't be treated as interchangeable markets.


Where can I find current, detailed data on Florence separately from this comparison post?

This site maintains Florence as its own separately covered market with dedicated content, referenced but not restated in detail here. Check Florence's own market report and regulatory posts directly for current, town-specific figures.


Work with Crest & Cove Creative

Marketing a Yachats property with Florence's dune-recreation identity — or vice versa — attracts the wrong guest and produces mismatched-expectation reviews. Name the failure mode the guest can check on the listing.


A free marketing audit shows whether your listing is speaking to the right guest for the town it's actually in. Request yours to find out. Send the live listing draft and the facts you can actually cite.


Reach out at crestcove.co or (256) 998-7502.

Comments


bottom of page