Clark County's short-term rental ordinance, codified at Clark County Code Chapter 7.100, requires every licensed STR in unincorporated Clark County to operate a continuously running, street-facing security camera and dedicated noise monitoring devices at each property line and near any pool or spa, with both video footage and noise data retained for at least sixty days and produced to the county or law enforcement within forty-eight hours of a request. On August 18, 2026, county commissioners went further, approving an ordinance that requires booking platforms such as Airbnb and Vrbo to verify a property's license before accepting payment, effective September 2, 2026, with civil penalties of $500 for a first violation and $1,000 for each additional one against platforms that keep listing unlicensed units. A federal judge issued a preliminary injunction in December 2025 blocking enforcement of the county's license requirement and penalty structure, and the county voted in January 2026 to appeal, so hosts should not assume the underlying licensing mandate is settled even as platform-side enforcement moves forward. This guide explains which camera and noise-monitor equipment satisfies Chapter 7.100 as written, how STR security requirements interact with HOA design review in communities that allow short-term rentals, what data-retention discipline actually looks like in practice, and why STR camera systems differ meaningfully from a typical owner-occupied home alarm installation.
Short-term rental hosts in unincorporated Clark County are operating under more regulatory pressure in 2026 than at any point since the county's STR ordinance first took effect. A new ordinance approved August 18, 2026 targets the booking platforms directly — Airbnb, Vrbo, and similar services must now confirm a property holds a valid county license before processing payment for a reservation, and platforms that keep facilitating bookings for unlicensed units face civil penalties starting at $500 per violation. That platform-side enforcement is new. What isn't new, and what many hosts still get wrong, is the underlying security and surveillance equipment Clark County Code Chapter 7.100 has required of licensed short-term rentals for years: a functioning, continuously recording camera and dedicated noise monitoring hardware, both with strict data-retention and law-enforcement production requirements. This guide walks through what the equipment side of STR compliance actually requires, separate from the licensing paperwork itself.
Sources cited in this article: Clark County Code Chapter 7.100 (Short-Term Rental Units), Clark County Code Chapter 7.100.030, NRS Chapter 244, NRS 244.1545, NRS Chapter 648 (PILB alarm installer licensing), NRS Chapter 116 (HOA governing documents)
Clark County commissioners voted unanimously to approve a new ordinance aimed squarely at booking platforms rather than hosts directly. Starting September 2, 2026, platforms like Airbnb and Vrbo must verify that a listed property holds a valid county short-term rental license before accepting or facilitating payment for a reservation, and must display licensing information on listings. Platforms that keep processing bookings for unlicensed units face a $500 civil penalty for a first violation and $1,000 for each additional one. For hosts, the practical effect is that an unlicensed listing is now at real risk of being deactivated by the platform itself, not just cited by county code enforcement — a meaningfully different kind of pressure than in prior years.
This platform-verification rule sits on top of the licensing framework the county has run for years under Clark County Code Chapter 7.100, which governs short-term rental units in unincorporated Clark County. Operators pay annual license fees of $750 for units with three or fewer bedrooms, or $1,500 for units with more than three bedrooms, plus a $150 fee for a required safety inspection. The equipment requirements built into Chapter 7.100 — specifically the security camera and noise monitoring provisions — are the part of this framework most directly relevant to a home security discussion, and they are worth understanding in detail regardless of where the licensing litigation lands.
Chapter 7.100 requires each licensed short-term rental to maintain a functional, street-facing security camera that remains in continuous operation for the entire duration the property is rented. This is not a suggestion or a best practice — it is a licensing condition. Two specific operational requirements sit alongside the camera itself:
The ordinance carves out an exception for short-term rental units located within multifamily dwellings that have common entrances already surveilled or monitored — a single condo unit inside a monitored building complex is not necessarily expected to duplicate camera coverage the building already provides. For a standalone single-family STR, though, the camera requirement applies in full, and the street-facing orientation is specific: an interior camera, or an exterior camera pointed only at a side yard or backyard, does not satisfy the requirement on its own.
The most common compliance gap isn't the camera hardware — it's the storage plan behind it. Many consumer camera systems default to seven- or fourteen-day cloud retention unless the owner specifically upgrades to a longer-retention plan or adds local storage. A host who installs a perfectly good street-facing camera but leaves the default retention setting in place is technically out of compliance with the sixty-day requirement the moment footage older than two weeks gets overwritten. Before listing a property, hosts should confirm in writing — not assume from a marketing page — exactly how many days of footage their specific plan retains, and budget for whatever storage tier actually reaches sixty days.
Separate from the camera, Chapter 7.100 requires licensees to install noise monitoring devices at each property line, in both the front and rear yard, as well as in the vicinity of any outdoor pool or spa. Like the camera, these devices must operate continuously while the property is rented, and must alert the licensee or a designated local representative when sustained noise levels exceed the standards set out in the ordinance. Noise level data carries the same sixty-day retention and forty-eight-hour production requirements as camera footage.
This requirement applies regardless of whether the property has a pool — the front- and rear-yard property-line monitors are a baseline requirement, and pool/spa monitoring is additive for properties that have one. Noise complaints are, in practice, one of the most common triggers for STR code enforcement action in Clark County, and a documented noise monitoring system that shows a licensee responded to an alert is meaningfully different, from an enforcement standpoint, than a host with no monitoring at all who is relying entirely on neighbor complaints to know something went wrong.
A significant number of Las Vegas short-term rentals sit inside HOA-governed communities, and this is where county compliance and community governance can pull in different directions. Nevada regulates common-interest community governance under NRS Chapter 116, which gives HOAs enforcement authority over architectural and design standards laid out in their own CC&Rs. Two separate questions apply to any STR host inside an HOA:
Hosts operating STRs in design-controlled communities such as Summerlin, Anthem, MacDonald Highlands, or Lake Las Vegas should confirm both questions before listing a property, not after. A camera that satisfies the county but violates the HOA's design guidelines solves one compliance problem while creating another.
The sequencing problem here is the same one that trips up full-time residents installing cameras in design-controlled communities, just with an added layer: an STR host who mounts a stock white camera on a stucco wall to hit a listing deadline risks not only an HOA design review objection and a possible fine under NRS 116.31031, but also a county licensing gap if the camera has to come down for reinstallation mid-dispute. Because the Chapter 7.100 camera requirement is continuous — not a one-time inspection checkbox — any gap in coverage while equipment is being swapped or relocated for HOA compliance is itself a period where the license is arguably not being satisfied. The practical fix is the same one that applies to full-time residents: submit the design review application with the exact camera model, housing color, and mounting location before the unit is ever listed for booking, not after an HOA notice forces a redo.
It's worth being precise about the current legal status, because it's easy to overstate. A federal judge issued a preliminary injunction in December 2025 blocking Clark County from enforcing its short-term rental license requirement and the penalty structure tied to it. The county's Board of Commissioners voted on January 6, 2026 to appeal that injunction, meaning the underlying dispute over the county's licensing authority remains actively contested in federal court. The August 18, 2026 platform-verification ordinance is a separate enforcement tool, aimed at booking platforms rather than at hosts directly, and its September 2, 2026 effective date does not by itself resolve the pending appeal.
For a host trying to decide how seriously to take the camera and noise-monitor requirements right now, the practical answer is: treat them as fully in force. An injunction against one enforcement mechanism, under active appeal, is a thin foundation to build a compliance strategy on — especially when the equipment itself (a working camera, adequate storage, functioning noise monitors) is inexpensive relative to the licensing fees, and provides genuine security and liability benefit to the host independent of the litigation's outcome. Hosts with specific questions about current enforcement status should contact the county's Short-Term Rental division directly rather than relying on news coverage of the injunction alone.
Homeowners researching security installation in the Las Vegas valley are usually thinking about interior motion sensors, door and window contacts, and a monitored panel — the standard architecture of a residential burglar alarm system regulated under NRS Chapter 648 and, for installers operating in Clark County, registered under Clark County Code Chapter 6.76. STR compliance under Chapter 7.100 asks for something different and additive: exterior, street-facing surveillance with specific retention obligations, and dedicated noise monitoring hardware that has no equivalent in a typical owner-occupied installation. A host converting a primary residence to a short-term rental, or buying a property specifically to operate as one, should budget for both systems rather than assuming a standard interior-focused alarm setup covers the county's requirements. Regardless of which system is being installed, the installer doing the work needs an active PILB license under NRS Chapter 648 — that requirement doesn't change based on whether the property is owner-occupied or an STR.
There's also a monitoring-philosophy difference worth flagging. An owner-occupied alarm system is designed around the assumption that the person most likely to trip a sensor by accident is the homeowner, and the system's job is mainly to catch intrusion while the home is empty. An STR camera and noise-monitor setup is designed around a different assumption: the person inside the home during any given stay is a paying guest the host has never met, and the equipment's job is partly to document what happened for liability and dispute-resolution purposes, and partly to catch policy violations — unauthorized additional guests, unpermitted parties, noise that risks a neighbor complaint — while they're still in progress rather than after the fact. That distinction is why the county mandates specific exterior and noise-monitoring hardware for STRs rather than simply requiring "a security system": the compliance goal is documentation and early alerting, not just intrusion detection.
Cost-wise, hosts should expect the incremental equipment on top of an existing alarm system — a dedicated street-facing camera with adequate cloud storage, plus noise monitors at each property line and near a pool if present — to run into several hundred dollars in hardware alone, before installation labor and any HOA-driven finish upgrades. Weighed against a first-violation platform penalty, a county citation, or the cost of a canceled listing after an unlicensed-platform deactivation once the September 2, 2026 verification rule takes effect, the equipment cost is the smaller number in almost every scenario.
Pulling the requirements together, a Clark County STR host should be able to answer yes to each of the following before listing a property:
Hosts weighing a full system upgrade rather than adding STR-specific hardware to an existing setup can review general installation options for Summerlin or other Vegas-area communities as a starting point, then layer the street-facing camera and noise monitoring equipment Chapter 7.100 specifically requires on top of whatever baseline system the property already has.
Clark County Code Chapter 7.100 does not mandate a specific manufacturer or model. It requires that the camera be street-facing, remain in continuous operation while the property is rented, and that footage be retained for at least sixty days and be producible to the county or a law enforcement agency within forty-eight hours of a request. Any camera system that reliably meets continuous-recording uptime and sixty-day storage — whether that's cloud storage with a long-retention plan or a local NVR with sufficient drive capacity — satisfies the letter of the requirement. The practical failure point for most hosts isn't camera quality, it's storage: a cheap cloud plan that only retains seven or fourteen days of footage does not meet the ordinance even if the camera itself records fine.
Yes. Chapter 7.100 requires noise monitoring devices at each property line in both the front and rear yard regardless of whether the property has a pool or spa — the pool/spa monitoring requirement is in addition to, not instead of, the property-line devices. The monitors need to operate continuously while the unit is rented and alert the licensee or local representative when sustained noise exceeds the ordinance's noise standards. Like the camera footage, noise level data has to be kept for at least sixty days and produced within forty-eight hours of a county or law enforcement request.
In most cases, yes, and this is one of the most commonly missed steps by STR hosts. The Chapter 7.100 camera and noise-monitor requirement is a county licensing condition; it says nothing about whether your HOA's governing documents, enforceable under NRS Chapter 116, allow exterior camera or sensor hardware without a design review submission. Communities that permit short-term rentals at all — and many master-planned Vegas HOAs restrict or prohibit them entirely, separate from the county licensing question — still typically require exterior equipment to go through the same architectural review process as a full-time resident's camera installation. Hosts should confirm both that STRs are permitted under the community's CC&Rs and that the required street-facing camera can be mounted in a design-review-compliant location and finish before listing the property.
Be careful here. A federal judge issued a preliminary injunction in December 2025 that stopped Clark County from enforcing its license requirement and associated penalty structure, and the county voted on January 6, 2026 to appeal that ruling — meaning the underlying legal question is not fully resolved. Separately, the county's August 18, 2026 ordinance targeting booking platforms is a different enforcement mechanism aimed at Airbnb, Vrbo, and similar platforms rather than directly at hosts, and takes effect September 2, 2026. Hosts should not treat the injunction as blanket permission to skip licensing or equipment requirements; the safer approach, given active litigation and a pending appeal, is to maintain full compliance — including the camera and noise monitor requirements — and consult the county's Short-Term Rental division or an attorney about the current enforcement status before making any decision based on the litigation.
Partially, but not automatically. A standard owner-occupied alarm system in Las Vegas typically emphasizes interior motion sensors, door and window contacts, and a monitored panel tied to a central station — none of which, by itself, satisfies Chapter 7.100's specific street-facing camera and property-line noise monitor requirements. An STR host generally needs to add a dedicated exterior camera positioned to face the street (not just a doorbell camera with a narrow field of view) and separate noise monitoring hardware, on top of whatever interior security system the property already has. Any installer doing the work — whether adding STR-specific equipment or a full system — still needs to hold an active PILB license under NRS Chapter 648, the same requirement that applies to every alarm installation in the state.
Failing to retain footage or noise data for the required sixty days, or being unable to produce it within forty-eight hours of a county or law enforcement request, is a separate compliance failure from simply owning a camera — and it's the piece hosts most often overlook because it depends on storage configuration rather than hardware. A camera that works fine but is set to a default seven-day cloud retention plan, or an NVR with a hard drive too small to hold sixty days of continuous street-facing footage, puts the license out of compliance even though the equipment itself is functioning normally. Hosts should verify their specific storage plan's retention window in writing, not assume a manufacturer's default settings meet the county's sixty-day floor.
Need to discuss your specific Las Vegas home security situation with a licensed Nevada PILB installer? Use the form above or call (702) 555-0199 for a free, no-obligation quote.
No pressure, no obligation. Licensed Nevada PILB installers respond within one business hour with a free in-home site survey.