Washington, DC legal and installation guide

Washington, DC Dash Cam Rules: Mounting and Audio

Why a standard windshield installation should not be copied into the District without reviewing DC’s specific mounting and privacy provisions.

Reviewed August 2, 2026Primary sources linkedInstaller-focused guidance

Front dash camera mounted high behind a vehicle rear-view mirror — Example mounting position for evaluating driver visibility; the photograph is an installation example and is not presented as a DC roadway.

Quick answer

Washington, DC needs a different mounting analysis

Installer takeaway: DC’s regulation text is broader than the familiar “do not obstruct the driver’s view” rule. It addresses objects attached to or suspended from the windshield and rear-view mirror, so a standard adhesive windshield mount should not automatically be treated as acceptable.

Two provisions matter. 18 DCMR §731 addresses nontransparent material on vehicle glass. More importantly for a dash camera, 18 DCMR §2213.7 states that a vehicle operated on District highways shall not have an object attached to or suspended from the rear-view mirror, mirror bracket, windshield, rear window or front side windows.

Practical consequence: a position that works in Virginia may still raise a different issue after crossing into DC. The installation plan should be reviewed for the District, not copied from a neighboring-state template.

Mounting options

Questions to resolve before installation

Is glass attachment necessary?

Consider whether a vehicle-specific, dashboard or integrated mounting solution can provide a useful view without attaching an object to regulated glass or the mirror bracket.

Will the camera remain secure?

A legal-placement concern should not be solved with a loose mount. The camera must remain stable in braking, heat and vibration.

Are sensors and airbags clear?

Do not interfere with the factory forward camera, defroster, passenger airbag deployment area, instrument visibility or vehicle controls.

Can the route cross jurisdictions?

Vehicles based in Maryland or Virginia but routinely driven into DC should be planned for the strictest recurring jurisdiction.

Audio and privacy

DC generally recognizes participant consent, but use still matters

D.C. Code §23-542 includes an exception where a person is a party to the communication or one party has given prior consent, unless the interception is for a criminal, tortious or other injurious act. That does not eliminate privacy, employment, rideshare-policy or cross-border questions.

Make the microphone setting a deliberate choice.
Use clear notice for passengers, employees and fleet drivers.
Limit footage access and avoid unnecessary public sharing.
Apply a more conservative consent practice when the vehicle enters Maryland.

For rideshare and fleet use: write down who controls the account, who receives event alerts, how long clips are retained and how drivers or passengers are notified.

Installation workflow

A DC-ready pre-installation review

Identify every jurisdiction in which the vehicle normally operates.
Photograph the proposed mounting area from the driver’s seated position.
Check the proposed attachment method against current DC rules.
Confirm the lens view without compromising safe operation.
Document microphone, cloud access and retention settings.
Recheck the camera after heat exposure and normal driving.

Primary sources

Read the current District provisions

18 DCMR §2213 — obstruction of driver view and objects attached to vehicle glass or mirror hardware.

18 DCMR §731 — windshields and nontransparent material.

D.C. Code §23-542 — interception and participant-consent provisions.

After a DC-area collision: Use the emergency evidence kit and footage-preservation guide before copying or sharing the recording.

This page is educational installer guidance, not legal advice. DC mounting language is unusually broad; obtain qualified legal guidance when a definitive interpretation is required.

Discuss a DC installation Send vehicle details