TODAY’S PAPER | March 22, 2026 | EPAPER

Justin Timberlake arrest video released after legal battle over privacy

Justin Timberlake’s 2024 arrest video is released after court ruling, revealing failed sobriety tests and details


Pop Culture & Art March 22, 2026 1 min read
Photo: Reuters

Justin Timberlake’s long-contested arrest footage has been released following a court decision, ending a months-long legal effort to keep the video private. 

The bodycam footage, made public on March 21, 2026, stems from his June 18, 2024 arrest in Sag Harbor.

The video captures the Grammy-winning artist during a traffic stop in which officers observed him allegedly running a stop sign and failing to maintain his lane. During field sobriety tests, Timberlake appears visibly nervous and unsteady, telling officers the exercises were “really hard” while attempting to walk in a straight line and balance on one leg. He also admitted to having consumed one martini prior to driving.

The arrest initially led to a driving while intoxicated (DWI) charge, which was later reduced. Timberlake ultimately pleaded guilty to impaired driving in September 2024. His sentence included a $500 fine, 25 hours of community service, and a 90-day suspension of his driver’s license.

Timberlake had filed a legal challenge in March 2026, arguing that releasing the footage would cause reputational harm and violate his privacy. However, after negotiations, he agreed to the release of a redacted version. Court filings indicated the footage did not constitute an unwarranted invasion of privacy under state law.

The video also shows interactions with individuals at the scene, including designer Estee Stanley, who was present at the time of the arrest.

The release concludes a 21-month legal process and has reignited public discussion about celebrity accountability, privacy rights, and the broader implications of police bodycam transparency.

COMMENTS

Replying to X

Comments are moderated and generally will be posted if they are on-topic and not abusive.

For more information, please see our Comments FAQ