How Delhi's Government Archives Ended Up Flooded With Duplicate Images — And Why It's Finally Being Fixed

Delhi's public records infrastructure has a clutter problem that predates the current AAP government and stretches back through multiple administrations. Officials at the Delhi Secretariat on IP Estate are now undertaking what is being described internally as a systematic duplicate-image replacement drive — a cleanup of digitised government documents in which the same scanned pages, photographs, and identity records were stored, in some cases, four or five times over across different departmental servers.

The problem matters urgently right now because Delhi is in the middle of a push to integrate services across platforms. The Delhi Metro Rail Corporation's Phase 4 expansion, which is adding corridors through Janakpuri West, Tughlakabad, and Aerocity, requires coordinated land-acquisition and heritage-clearance documentation. When those files contain duplicate scanned images — often scanned at different resolutions by different agencies at different times — the administrative trail breaks down and approvals stall.

How the Duplication Got So Bad

The roots of the problem go back to at least 2010, when the Delhi government's Department of Information Technology launched an early digitisation push under the e-District project, a centrally funded scheme designed to move revenue and welfare records online. That effort was followed by at least two subsequent scanning initiatives — one under the National Mission for Clean Ganga that affected Yamuna-related land records in areas like Wazirabad and Okhla, and another under the Smart Cities framework that touched Old Delhi neighbourhoods including Chandni Chowk and Ballimaran.

Each initiative used its own scanning vendor, its own naming convention, and its own file server. Nobody mandated deduplication before upload. By the time the Delhi government's centralised Digilocker-linked portal went live, the backend was ingesting files from at least three legacy systems that had never been reconciled. The result: a single ration card from a family in Seemapuri might exist as six separate JPEG images across four databases, each slightly different in file size and metadata.

The financial cost is not trivial. Cloud and on-premise storage for Delhi government departments has expanded significantly over the past five years, with procurement records showing storage contracts running into tens of crores annually across the GNCT (Government of the National Capital Territory) departments. Redundant image files are a direct contributor to that overhead, according to the logic of the current cleanup exercise, though precise savings projections have not been made public.

What the Cleanup Actually Involves

The duplicate-image replacement process, as understood from departmental circulars, works in two stages. First, automated hashing tools compare every stored image file and flag matches above a set similarity threshold. Second, a designated record keeper — in practice, a junior official at the district level, such as at the South Delhi District Collectorate in Saket or the North-West district office near Rohini Sector 18 — reviews flagged duplicates and authorises replacement with a single canonical version.

The canonical version is typically the highest-resolution scan with the most complete metadata. Older, lower-quality duplicates are then retired rather than deleted outright, moved to a cold-storage archive in keeping with the Public Records Act, 1993, which mandates retention periods for government documents of varying classifications.

The Delhi government set an internal deadline of March 2026 to complete the first phase of the exercise for revenue and identity records. That deadline was missed, and the work is continuing into the current quarter. Heritage records from the Archaeological Survey of India's protected zones in Old Delhi — including properties along Netaji Subhash Marg — fall under central government jurisdiction and are handled separately, adding another layer of coordination complexity between the AAP administration and the Modi government's ministries.

For residents, the practical upshot is that certificate requests, property-mutation applications, and Below Poverty Line card renewals processed through the Delhi e-District portal should, in theory, become faster once the backend is clean. Officials handling duplicate flags at the Shahdara and Dwarka sub-divisional offices have been instructed to prioritise pending welfare-scheme applications first. Citizens waiting on documents tied to Old Delhi's heritage-zone properties — where digitisation has been most inconsistent — may wait longer, but the endpoint, at least, is now clearly mapped.