How DC's Digital Archives Ended Up Riddled With Duplicate Images — And What Officials Plan to Do About It

Washington's municipal digital infrastructure has a clutter problem. Thousands of duplicate photographs — many capturing the same streets, events, and city landmarks from nearly identical angles — have accumulated across at least a dozen District of Columbia agency servers, driving up storage costs and making public records requests slower and more complicated than they need to be. The issue, which city technology officials have been quietly working to address since late 2024, has come into sharper focus this summer as the Bowser administration rolls out a consolidated asset management protocol affecting agencies from the DC Office of Planning to the District Department of Transportation.

The timing matters. With federal funding streams to the District under pressure from ongoing restructuring at the federal level — including efficiency reviews that have already rippled through agencies sharing office space near L'Enfant Plaza and the Navy Yard corridor — the city cannot afford to waste storage bandwidth or staff hours on redundant files. A single full-resolution event photograph can run between 8 and 25 megabytes. Multiply that by tens of thousands of duplicates and the cumulative drain on server capacity becomes a genuine budget line, not just a housekeeping annoyance.

A Problem Built Over Decades

The roots of the duplication crisis stretch back to the early 2000s, when individual DC agencies began digitizing their photo archives independently, often using different file-naming conventions and metadata standards. The DC Public Library's Washingtoniana Division, which maintains historical photograph collections covering neighborhoods from Anacostia to Petworth, operated on a completely separate system from, say, the DC Office of Motion Picture and Television Development, which catalogues production stills and location scouting images. Nobody built a bridge between them.

Two rounds of federal digitization grants — one administered through the Institute of Museum and Library Services around 2009 and another through a National Endowment for the Humanities program roughly a decade later — pushed agencies to scan faster rather than smarter. Staff under grant deadlines uploaded images in bulk. If a photograph of the Martin Luther King Jr. Memorial Library on G Street NW had already been scanned twice by two different departments, nobody's system flagged it. The result was redundancy baked into the architecture at the point of creation.

The problem compounded during the pandemic, when remote work forced agencies onto cloud platforms in a hurry. The DC government migrated significant portions of its data infrastructure to cloud storage beginning in March 2020. Agencies that had never compared notes on file management were suddenly uploading to shared environments — and discovering, often too late, that their archives overlapped substantially with colleagues they'd never coordinated with before.

What the Fix Actually Looks Like

The current remediation effort centers on a de-duplication protocol being piloted by the DC Office of the Chief Technology Officer, which is based at 200 I Street SE. The protocol uses hash-matching software to identify byte-identical files and flagging tools for near-duplicate images — photographs that are technically distinct files but functionally the same picture. Staff then review flagged images before deletion, a step that archivists at institutions like the Historical Society of Washington DC, headquartered on Massachusetts Avenue NW, pushed hard to include after early drafts of the plan proposed automated deletion without human review.

The practical stakes for residents are real. Public records requests filed through the DC government's online portal — which processed more than 14,000 requests in fiscal year 2024 according to the DC Office of Open Government's annual report — are sometimes delayed when agency staff must manually sort through duplicate files to locate a specific image. Streamlining the libraries should, in theory, cut response times.

Officials plan to complete the pilot phase covering three agencies by September 2026, with a district-wide rollout targeted for fiscal year 2027. Residents and journalists who regularly file FOIA requests with DC agencies should expect some disruption to image-retrieval systems during the transition window — and should plan to follow up directly with the relevant agency's records officer rather than assuming an automated response covers their request. The DC Office of Open Government maintains a public directory of agency records officers updated quarterly.