Moscow's Digital Archive Problem: The Numbers Behind the City's Duplicate Image Crisis

Moscow's municipal digital infrastructure is carrying a dead weight measured in terabytes. An internal audit completed in June 2026 by the Department of Information Technologies — the city agency headquartered on Tverskaya Street — found that duplicate and near-duplicate images account for an estimated 34 percent of total storage consumed across the city's public-facing digital platforms, a figure that translates to roughly 180 terabytes of redundant data sitting on servers maintained under the Gosuslugi Moskvy service umbrella.

The problem sounds technical. The cost is not. Storage contracts for municipal server infrastructure in Moscow run on rolling annual terms, and industry pricing for enterprise-grade managed cloud storage in Russia currently sits at around 4,500 rubles per terabyte per month. At that rate, the city is spending in the region of 810,000 rubles every month to house files it does not need — images uploaded multiple times by different departments, slightly cropped variants of the same photograph, and format conversions of identical source material piling up without any automated deduplication process in place.

How the Backlog Built Up

The root cause is structural rather than careless. Moscow's city communications apparatus expanded rapidly between 2019 and 2024 as district administrations from Troitsk in the southwest to Mitino in the northwest each built semi-autonomous content teams. Each team maintained its own upload portal feeding into the city's centralised Moscow Media content management system. Without cross-departmental deduplication rules, the same event photograph — say, a ribbon-cutting at a newly resurfaced section of Enthusiasts Highway — might enter the system four or five times, tagged differently by different administrators and therefore invisible to basic filename-matching filters.

The Moscow Urban Forum, held annually at Zaryadye Park near the Kremlin embankment, has itself become a case study in the problem. Post-event image libraries from the 2022, 2023, and 2024 editions alone contain over 12,000 files flagged by the June audit as exact or near-exact duplicates — roughly 40 percent of the total photos submitted from those three events combined. Forum organisers used at least three separate upload channels over that period.

Digital asset management specialists point to a specific technical threshold: perceptual hashing algorithms, which compare images by visual content rather than filename, can typically identify duplicates with more than 95 percent accuracy even when files have been resized or re-compressed. The audit found that Moscow's current CMS deploys only basic MD5 checksum matching, which catches byte-for-byte identical files but misses the far more common category of near-duplicates — the same image saved as both a JPEG and a PNG, or cropped to different aspect ratios for different publishing channels.

What the City Plans to Do About It

The Department of Information Technologies has outlined a remediation timeline running through Q1 2027. The first phase, scheduled for completion by 1 October 2026, involves deploying a perceptual hashing layer across the Moscow Media CMS and flagging existing duplicates for human review. A secondary automated purge — removing files confirmed as exact duplicates with no active links to published pages — is planned for November 2026, ahead of the next municipal budget cycle.

The practical implications for Muscovites are indirect but real. City websites including mos.ru and the Aktivny Grazhdanin civic engagement platform both draw images from the same bloated asset pool. Page load times on mos.ru, benchmarked internally at 3.2 seconds on average for image-heavy pages as of May 2026, are partly attributable to unoptimised asset delivery from cluttered libraries. The deduplication project is expected to reduce the active image library by at least 25 percent, which project planners say should bring average load times below 2 seconds — a standard threshold for acceptable government-portal performance.

For the city's 180-odd district content teams, the practical change will be a new mandatory duplicate-check step before any upload is confirmed. Training sessions for content administrators are being coordinated through the Moscow School of Management SKOLKOVO digital governance programme, with the first cohort of 60 staff members scheduled to complete the module by 15 August 2026. The savings, if the timeline holds, would free up roughly 9.7 million rubles annually — enough, budget documents note, to fund a full additional year of the city's open-data portal expansion.