SF City Hall's Duplicate Image Problem: What Happens Next and the Key Decisions Ahead

San Francisco's Department of Technology has identified more than 4,000 duplicate images cluttering the city's public-facing digital infrastructure, according to an internal review completed this spring — a sprawling mess of redundant files spread across sf.gov, the Planning Department's project portal, and the SFMTA's public maps database. The finding has set off a quiet but consequential debate inside City Hall over how to clean it up, who owns the problem, and whether the fix will cost the city money it doesn't have.

The timing is lousy. Mayor Daniel Lurie took office in January pledging to modernize city services after years of stagnation under the previous administration, and his budget office is already navigating a structural deficit that has forced cuts to departments from the Public Utilities Commission to the Department of Public Health. Duplicated digital assets may sound like a housekeeping issue, but city IT officials say the redundancy inflates server storage costs, slows page-load times on services residents actually rely on, and creates version-control chaos when emergency information — like evacuation maps during wildfire season — needs to be updated fast.

What the Audit Actually Found

The review, conducted by the Department of Technology's Digital Services team in partnership with vendors operating out of the city's Civic Center offices on Van Ness Avenue, flagged duplicate images on at least 14 separate city subdomains. The Planning Department's portal alone contained roughly 900 redundant image files, many of them project renderings uploaded multiple times by different staff members with no centralized asset management system in place. The SFMTA's transit map library had similar problems, with some route graphics stored in three or four separate locations simultaneously.

The city has been running on a content management platform that predates the 2020 pandemic. A contract to upgrade the underlying system — estimated at roughly $2.3 million over three years, according to budget documents circulated ahead of the June Board of Supervisors hearing — has been stalled since late 2025 amid questions about vendor selection. That delay is now directly relevant, because city IT staff say a modern digital asset management layer could automate duplicate detection and prevent the problem from recurring. Without it, any manual cleanup is a stopgap.

The Decisions That Will Define the Outcome

Three choices now sit in front of city leadership. First, the Department of Technology must decide whether to proceed with a manual purge of duplicate files before the contract upgrade is resolved — a faster but potentially wasteful approach if the new system reorganizes asset storage anyway. Second, the Board of Supervisors' Government Audit and Oversight Committee, chaired this session by a Mission District supervisor, will need to decide whether the stalled contract moves forward before the fiscal year closes on July 31. Third, the Lurie administration has to answer whether duplicate image management falls under the existing Digital Equity Initiative or requires a separate procurement line.

None of these are glamorous decisions. But residents who use the sf.gov permit portal — particularly small business owners in the Tenderloin and SoMa who have repeatedly flagged slow load times when submitting documentation — have a direct stake in the outcome. The San Francisco Small Business Commission flagged digital service latency as a recurring complaint in its March 2026 report to the Board of Supervisors.

The Department of Technology has until September 15 to submit a corrective action plan under a directive issued by the City Administrator's office. That deadline gives the Digital Services team roughly ten weeks to propose either the manual cleanup, the accelerated contract, or a hybrid approach. Advocates for open government, including staff at the San Francisco chapter of Code for America who operate out of offices near Civic Center, have pushed for the city to publish the full audit findings so outside developers can propose lightweight deduplication tools. Whether city officials open that door — or keep the review internal — may be the most consequential single decision of the bunch.