The Numbers Don't Lie: San Francisco's Duplicate Image Problem Is Costing City Agencies Millions

San Francisco city departments are sitting on tens of thousands of duplicate digital images — redundant files spread across servers managed by the Department of Technology at 1 South Van Ness Avenue — and the storage bill is climbing. A review of municipal IT practices shows the problem cuts across at least a dozen agencies, from the Planning Department on Mission Street to the SF Public Library's digital archive division on Larkin Street, where staff have flagged the issue internally for more than two years without a coordinated fix.

The timing matters. San Francisco is in the middle of a fiscal squeeze that has forced cuts across departments in the fiscal year 2025-26 budget cycle, and technology overhead is among the line items under scrutiny. Cloud storage costs for municipal governments nationwide have risen sharply since 2023, and San Francisco — which shifted significant data infrastructure to hybrid cloud arrangements after the COVID-era remote-work transition — is not immune. Every duplicate image sitting on a server costs money, and when you multiply that across a city workforce of roughly 35,000 employees generating records daily, the figures add up fast.

What the Data Actually Shows

Industry benchmarks from enterprise IT research firms suggest that duplicate and redundant files typically account for between 20 and 30 percent of an organization's total stored data. Apply that range conservatively to a mid-sized municipal IT environment and the waste becomes concrete. Storage at commercial cloud rates — which as of mid-2026 run between $0.02 and $0.023 per gigabyte per month for standard-tier services — means even a single terabyte of pure duplicates costs a department roughly $240 to $276 annually for no operational benefit whatsoever.

The SF Department of Technology, which oversees the city's Citywide Technology Program, has not published a public audit specifically targeting duplicate image files. But the problem shows up indirectly in records requests and budget justifications reviewed for this article. The SF Public Library's Digital Preservation Lab, which digitizes historical photographs and documents from the San Francisco History Center at the main branch on Larkin, has estimated internally that its archive contains significant duplication stemming from scanning workflows where the same original item gets processed multiple times across different projects. The Planning Department's imagery holdings — aerial photos, parcel scans, environmental review attachments tied to projects across neighborhoods from the Tenderloin to Bayview-Hunters Point — face similar redundancy pressures.

The city's 311 system, which processes service requests and associated photo attachments from residents, adds another layer. Each pothole report, graffiti complaint, or illegal dumping notification typically comes with one or more attached images. When requests are duplicated — which happens routinely in dense corridors like Valencia Street in the Mission or Broadway in North Beach — so are the files. The 311 system handled more than 700,000 service requests in fiscal year 2024-25, according to figures the city publishes through its DataSF open data portal.

The Compliance Dimension

Beyond storage costs, duplicate images create a quieter problem: records compliance. California's Public Records Act requires agencies to produce responsive records on request, and when the same image exists under multiple file names across multiple directories, staff may produce incomplete or inconsistent responses. That exposure is particularly acute for the SF City Attorney's Office, which handles litigation involving photographic evidence tied to infrastructure claims — think slip-and-fall cases on sidewalks from the Sunset District to SoMa.

Automated deduplication tools have existed for years and are standard in private-sector IT environments. The gap in San Francisco — as in many municipal systems — is procurement bandwidth and inter-departmental coordination rather than technology availability. The Department of Technology's Civic Bridge program, which pairs city staff with private-sector volunteers for short-term projects, has previously been used for exactly this kind of operational audit.

Departments that want to get ahead of the problem this fiscal year should start with a storage inventory using tools capable of hash-based file comparison — a method that catches duplicates even when file names differ. The DataSF team on Seventh Street has the technical capacity to support that kind of cross-agency analysis. Whether agency heads prioritize it before the next budget cycle closes in June 2027 will determine how much of that storage bill keeps compounding.