Seattle's Office of City Clerk moved this week to address a sprawling duplicate image problem inside the city's digital archive, a system that holds more than 4 million records spanning land-use permits, council proceedings, and historic photographs stretching back to the 1890s. The cleanup, which began in earnest on June 30, targets an estimated 340,000 redundant image files that have accumulated across multiple storage servers, slowing retrieval times and complicating public records requests filed under Washington State's Public Records Act.
The timing matters. Seattle has fielded a rising volume of public records requests over the past two fiscal years, and duplicate files have repeatedly surfaced as a source of delay. When a single scanned photograph exists in three or four versions across different folders — sometimes with mismatched metadata — staff must manually verify which copy is authoritative before releasing it. That process adds hours to each affected request.
What Triggered the Push This Week
The immediate catalyst was a routine audit of the Clerk's Laserfiche content management platform, the same system used by the Seattle City Council to publish legislative documents. Technicians identified that a batch import run in late May 2026 — designed to migrate approximately 18,000 historic Capitol Hill neighborhood planning images from an older SharePoint archive — had instead created duplicate entries throughout three linked repositories. The error was caught on June 28. By July 1, a four-person IT team drawn from the Department of Finance and Administrative Services was reassigned to run deduplication scripts and manually verify flagged files.
The Capitol Hill images in question document zoning changes and streetscape surveys conducted between 1998 and 2011, material frequently requested by architects, developers, and historians working on projects in the 23rd Avenue corridor and around Broadway. Researchers at the Seattle Municipal Archives, located on the fourth floor of Seattle City Hall at 600 Fourth Avenue, say the confusion has occasionally meant sending requesters the wrong version of a scanned map — sometimes a lower-resolution draft rather than the final certified document.
The Puget Sound Regional Council, which draws on city archive data for its regional growth modeling, flagged the problem to city staff in March 2026 after receiving inconsistent file sets in response to two separate data requests. That complaint accelerated internal discussions about a permanent deduplication protocol.
Scope of the Problem and Next Steps
Across the full archive, city IT staff estimate that roughly 8 percent of all image files stored as of January 2026 have at least one exact or near-exact duplicate. The deduplication project is budgeted at $112,000 for this fiscal year, covering contractor hours, software licensing for a hash-based comparison tool, and staff overtime. That figure was approved as part of the Clerk's 2026 operating budget passed by the City Council in November 2025.
The Office of City Clerk plans to complete the first phase — covering all permit-related imagery for the Capitol Hill, South Lake Union, and Chinatown-International District neighborhoods — by August 15. A second phase, addressing council meeting recordings and committee hearing photos, is slated for the fourth quarter of 2026. Staff are also piloting an automated ingestion rule within Laserfiche that would flag potential duplicates at the point of upload, rather than discovering them months or years later during audits.
For residents and researchers who regularly request historical photographs or land-use documents from the Municipal Archives, the practical advice is straightforward: if a records request submitted before July 1 returns image files that look mismatched in resolution or metadata, contact the Clerk's office directly at 206-684-8344 to flag the file set for re-review. Staff are maintaining a dedicated intake queue for requests affected by the May migration error through the end of July. The Clerk's office has also posted a notice on its Seattle.gov records portal explaining the issue and the expected timeline for resolution.