Louisville vs Jeffersonville: Conditional Use Is Not Indiana's File
Updated: Sep 2
Louisville and Jeffersonville sit on opposite banks of the Ohio River, close enough that a host managing properties in both cities can look out at one from the other. That proximity makes it tempting to treat the two markets' regulatory requirements as roughly interchangeable — confirm one desk's rules, apply them loosely to both properties, and move on. That shortcut doesn't hold up, and this page exists to spell out exactly why.
Louisville's short-term rental registration runs through the Louisville Metro Office of Planning and Design Services, with a Conditional Use Permit required specifically for properties in Old Louisville, in Limerick, and for any non-owner-occupied property regardless of neighborhood. Jeffersonville sits under its own separate Indiana process entirely, with its own desk, its own forms, and — as far as this pass can confirm — its own fee schedule that this page does not attempt to guess or estimate.
The two cities' revenue figures land close together on the extract this page draws from: Louisville's typical listing earned about $29,490 last year from 2,167 active rentals, while Jeffersonville's typical listing earned about $29,991 from 187 active rentals, both on the same August 2025 through July 2026 window. That closeness in the headline number is exactly what makes it easy to assume the underlying compliance requirements are similarly close. They are not, and this page keeps the two files separate throughout.
This is not legal advice. It is a plain accounting of what Louisville's registration desk specifically requires, paired with a clear statement of what this pass does and doesn't know about Jeffersonville's separate process, so a host with property on either side of the river — or both — knows exactly which file to open for which parcel.
Louisville's Desk: Planning and Design Services
Louisville Metro Office of Planning and Design Services holds annual short-term rental registration and the CUP process for the city. That is the single desk a Louisville host needs on file, and it is the desk responsible for confirming current fees, current forms, and current renewal timing for any Louisville property.
A Conditional Use Permit through that office is required for properties in Old Louisville, for properties in Limerick, and for any non-owner-occupied property regardless of which neighborhood it sits in. A property that falls under more than one of those triggers — a non-owner-occupied unit in Old Louisville, for instance — still only needs one CUP process, confirmed on all applicable grounds with the same desk.
louisvilleky.gov lists the fee structure for that CUP process specifically: a $200 pre-application fee, followed by a formal application fee of $560 for an owner-occupied property or $1,260 for a non-owner-occupied one. Confirm remaining annual registration dollars separately on the Planning page, since a $100 brief and a $250 aggregator clip both circulate near this topic without being the confirmed remaining annual fee itself. On top of Planning and Design Services entirely, a Louisville host also has to register separately with the Louisville Metro Revenue Commission for the tax side of operation.
Jeffersonville's Desk: A Separate File, Not a Louisville Mirror
Jeffersonville sits under its own Indiana registration process, run through its own local desk rather than any Louisville office. This pass does not guess remaining Jeffersonville license counts, fees, or CUP-equivalent requirements — where this page doesn't have a confirmed figure for Jeffersonville's own process, it says so plainly rather than assuming Louisville's structure carries across the state line.
That distinction matters practically: a Louisville CUP packet — with its Old Louisville and Limerick neighborhood triggers, its $200 and $560-or-$1,260 fee structure, and its non-owner-occupied trigger — is already the wrong exhibit for a Jeffersonville property, even if the two addresses sit within walking distance of each other across the Big Four Bridge. Indiana's registration framework, county involvement, and fee schedule are governed by an entirely different set of local rules that a host needs to confirm directly with the Jeffersonville and Clark County offices handling that side of the river.
A host with a Jeffersonville property should treat that confirmation the same way a Louisville host treats a call to Planning and Design Services: as the first step, not an afterthought, and as a step that produces a written, dated confirmation rather than an assumption carried over from what a similar-looking property across the river requires.
Can a Listing Scrape Substitute for Calling Either Desk?
No, and this is worth stating plainly because it's a common shortcut. A licensed-share indicator pulled from a listing platform, or a general summary scraped from a secondary website, is not the same thing as a confirmed registration or CUP status from the actual city desk. Display what the ordinance actually asks for on the listing once registration is genuinely complete, not a badge borrowed from a platform's own labeling system.
This matters more, not less, in a two-city situation like Louisville and Jeffersonville, where a scrape covering one city's general short-term rental landscape can easily blend details from both without flagging the difference. A host relying on that kind of general summary risks applying Louisville's CUP triggers to a Jeffersonville property, or assuming a Jeffersonville fee structure applies to a Louisville one, simply because the source material didn't clearly separate the two cities' requirements.
The reliable path in both directions is the same: identify which city the parcel actually sits in, call that city's specific registration desk, and get current requirements and fees confirmed in writing before advertising. That process takes longer than skimming a scrape, but it produces a compliance record that actually holds up if either city's enforcement ever asks a host to demonstrate current, confirmed registration status.
The Revenue Numbers, Kept on Separate Lines
Typical listings in Louisville earned about $29,490 last year from 2,167 active rentals, with an average night of $327, occupancy of 36.6 percent, and RevPAR of $111. Jeffersonville listings earned about $29,991 last year from 187 active rentals on the same window. Those two figures sit close together, but the supply bases behind them are dramatically different sizes — Louisville's market is more than eleven times larger by listing count — which means the two cities' underlying demand pools and competitive dynamics are not equivalent even though the top-line revenue numbers land near each other.
Hosts who underwrite Louisville stays should keep $29,490 on 2,167 listings, call the desk that matches the parcel, and leave Jeffersonville on a separate line — a discipline that applies to the revenue figure just as much as it applies to the registration paperwork. A packet that averages the two cities' revenue figures together, or that uses one city's growth trend to describe the other's trajectory, is building on a blended number that doesn't describe either market accurately.
File remaining 2026 packets on their own lines for each city: registration status, CUP status where applicable, fee amounts, and revenue figures should each carry their own city label and their own confirmation date, so a reader six months from now can tell at a glance which city a given number actually describes.
Why Proximity Doesn't Mean Shared Rules
It's worth pausing on why two cities separated by a single bridge end up with entirely independent registration systems in the first place. Louisville and Jeffersonville sit in different states, under different county governments, and under different municipal codes — the river isn't just a scenic boundary, it's a genuine jurisdictional line. Kentucky and Indiana each set their own frameworks for how local governments regulate short-term rentals, and Louisville Metro's own ordinance, with its CUP triggers and Planning and Design Services process, is a specifically Kentucky, specifically Louisville Metro creation.
That means a host can't reasonably expect Indiana's approach, or Jeffersonville's specific local implementation of it, to mirror Louisville's neighborhood-specific CUP triggers, its two-tier owner-occupied and non-owner-occupied fee split, or its particular combination of a Planning desk plus a separate Revenue Commission registration. Two cities a few minutes apart by car can have completely different definitions of what counts as a short-term rental, completely different registration cadences, and completely different enforcement approaches — and assuming otherwise is exactly the kind of gap that shows up during an actual compliance review rather than during casual research.
The safest mental model is to treat the river itself as the dividing line for every piece of paperwork, not just a scenic backdrop for a listing photo. A property's compliance file should be built around which side of that line the parcel physically sits on, full stop — not which side of the line the host happens to live on, not which city's numbers looked more favorable in an early revenue comparison, and not which city's requirements happened to be easier to research first.
Building Two Files Instead of One Blended Packet
For a host or investor working with a professional who is putting together a packet spanning both markets — a lender, a co-host manager, or an accountant handling both properties — the clearest ask is two separate sections rather than one blended overview. A Louisville section should carry Louisville's own registration status, CUP status if applicable, fee history, and Revenue Commission registration, each dated and sourced back to Louisville Metro's own desks. A Jeffersonville section should carry whatever that city's own desk has confirmed, kept entirely separate and never filled in by assumption from the Louisville side.
The same separation should extend to revenue reporting inside that packet. Louisville's $29,490 on 2,167 listings and Jeffersonville's $29,991 on 187 listings should each appear with their own extract citation and their own confirmation date, rather than as two rows in a single unlabeled table that a reader might later assume were measured the same way or drawn from the same underlying market. A packet built this way takes slightly longer to assemble than a single combined summary, but it holds up far better under scrutiny — from a lender, from either city's enforcement office, or simply from the host's own future self trying to remember which number applied to which property a year later.
None of this changes because the two properties happen to share a manager, a cleaning crew, or a marketing budget. Operational convenience across a two-city portfolio is reasonable and common; blending the underlying regulatory and revenue files is where the risk actually lives, and it's the piece worth keeping deliberately, permanently separate.
A useful habit is to name each file explicitly by city in every document that references it — a spreadsheet tab labeled "Louisville — Metro Planning" rather than just "Property A," a folder labeled "Jeffersonville — Clark County" rather than just "Rental 2." That small labeling discipline, repeated consistently across every document a host or their accountant touches, does more to prevent an accidental cross-city assumption than any amount of careful thinking done once and never revisited. Files that are clearly labeled stay separate even when the person maintaining them changes, or when months pass between updates.
The Cost of Getting This Wrong
The practical downside of blending these two files isn't abstract. A host who applies Louisville's CUP fee schedule to a Jeffersonville property either overpays for a permit that city doesn't actually require in that form, or underestimates what Jeffersonville's own process genuinely costs, either way based on the wrong city's numbers. A host who assumes Jeffersonville's simpler process applies to a Louisville property risks skipping a CUP application entirely on a property that actually requires one, which is a far more serious compliance gap than a budgeting error.
On the revenue side, a lender or partner reviewing a blended, unlabeled packet may reasonably ask which city's registration status backs which property's projected income, and a host unable to answer that question cleanly loses credibility on the whole packet, not just the ambiguous line. Two clearly labeled files, confirmed independently and dated, cost a little more time up front and save considerably more time, and risk, later.
Related Reading
More Louisville and Ohio River host reading on desks, calendars, and listing clarity.
Frequently Asked Questions
Do Louisville's registration rules apply to a Jeffersonville property?
No. Jeffersonville sits under its own separate Indiana registration process, run through its own local desk rather than any Louisville office. A Louisville CUP packet, with its specific neighborhood triggers and fee structure, is the wrong exhibit for a Jeffersonville property, and a host should confirm Jeffersonville's own requirements directly rather than assuming Louisville's process carries across the river.
What triggers a Conditional Use Permit in Louisville specifically?
A CUP is required for properties in Old Louisville, for properties in Limerick, and for any non-owner-occupied property regardless of neighborhood. A property meeting more than one of those criteria still only needs one CUP process. Properties outside those triggers should confirm their status directly with Louisville Metro Planning and Design Services rather than assuming exemption.
What does Louisville's CUP process cost?
louisvilleky.gov lists a $200 pre-application fee, followed by a formal application fee of $560 for owner-occupied properties or $1,260 for non-owner-occupied ones. Remaining annual registration dollars should be confirmed separately, directly on the Planning page, since secondary figures like a $100 brief or a $250 aggregator clip are not filed anywhere as that confirmed remaining fee.
What does Jeffersonville's registration process cost?
This pass does not have a confirmed figure for Jeffersonville's registration fees or CUP-equivalent process, and it deliberately does not guess one to fill that gap. A host with a Jeffersonville property should confirm current requirements and fees directly with the relevant Jeffersonville or Clark County desk rather than assuming Louisville's fee structure carries across the state line.
Can I use a listing scrape instead of calling each city's desk?
No. A licensed-share indicator from a listing platform or a general secondary summary is not the same as a confirmed registration or CUP status from the actual city desk. This is especially risky across two neighboring cities, since a scrape covering the broader region can blend Louisville and Jeffersonville details without clearly separating which requirement applies to which parcel.
How close are Louisville's and Jeffersonville's revenue figures?
Close in the headline number: Louisville's typical listing earned about $29,490 on 2,167 listings, while Jeffersonville's earned about $29,991 on 187 listings, both on the same extract window. But Louisville's supply base is more than eleven times larger, meaning the two markets' underlying demand pools and competitive dynamics are not equivalent despite the similar top-line figure.
Should I average Louisville's and Jeffersonville's revenue figures for a combined portfolio pitch?
No. Hosts underwriting Louisville stays should keep $29,490 on 2,167 listings on its own line and leave Jeffersonville's $29,991 on 187 listings on a separate line. Averaging the two produces a number that doesn't accurately describe either market, and a portfolio pitch spanning both cities should label each figure with its own city and its own extract citation.
Do I need to register separately with a tax authority in Louisville?
Yes. Beyond Planning and Design Services registration and any required CUP, a Louisville host also has to register separately with the Louisville Metro Revenue Commission for tax purposes. That is a distinct requirement from the land-use registration, and completing one without the other leaves a real compliance gap on the Louisville side specifically, regardless of how the Jeffersonville side of a portfolio is handled.
What's the safest approach for a host with property in both cities?
Treat each property as its own separate compliance file: confirm the specific city's registration desk, CUP or equivalent requirements, fee schedule, and tax registration independently, and keep dated, written confirmation for each. As a practical habit, never assume one city's confirmed requirement transfers to the other city's parcel, even when both properties sit within view of each other.
Work with Crest & Cove Creative
Same river, same extract window, and revenue figures close enough to blur together — but Louisville and Jeffersonville run on two completely separate registration desks. Name the failure mode the guest can check on the listing.
Let's build compliance-ready listing copy for whichever side of the river your property actually sits on, sourced from that city's own confirmed requirements. Name the failure mode the guest can check on the listing. Send the live listing draft and the facts you can actually cite.
Reach out at crestcove.co or (256) 998-7502.
Comments