Cairns Regional Council is moving to address a backlog of duplicate and orphaned images spread across its official websites, community portals, and internal document management systems — a problem that administrators say has been building since at least 2018, when the council migrated its primary content management platform to a new cloud-based environment.
The timing matters. Council is midway through a broader digital transformation program tied to the 2024–2028 Corporate Plan, and auditors reviewing asset registers ahead of the next budget cycle flagged duplicate media files as a source of avoidable storage costs and — more critically — a risk to public communications accuracy, particularly for disaster-preparedness pages used during cyclone season.
How the Problem Built Up
The roots of the duplication issue trace back to how different council directorates handled uploads independently. The Parks and Gardens team operating out of the Spence Street civic precinct maintained its own image libraries. So did the Cairns Water and Waste division, as well as the tourism-facing content team supporting the Cairns Convention Centre precinct on Wharf Street. When staff left or teams restructured, images were frequently re-uploaded rather than sourced from a central repository, creating near-identical files with different file names, compression ratios, and metadata tags.
The problem compounded during COVID-era staffing gaps between 2020 and 2022. Council's records indicate that during that window its public-facing web presence grew from roughly 4,200 indexed pages to more than 6,800, with community grant programs, reef-protection initiatives, and First Nations engagement materials all generating substantial new image content. Contractors brought in on short-term engagements had limited access to legacy storage systems, so they created new uploads by default.
The Cairns Airport precinct upgrade communications in 2021, and separately the rollout of the Better Bana neighbourhood renewal program in the southern suburbs, both generated large batches of photographs that were uploaded multiple times across different project microsites. By the time an internal review was completed in late 2025, technical staff had identified several thousand files flagged as probable duplicates within the council's primary digital asset management system.
What the Fix Actually Involves
Council's ICT directorate began a structured deduplication and metadata remediation project in the first quarter of 2026. The work involves automated hash-comparison tools to identify exact and near-identical duplicates, followed by manual review for images where context determines which version should be retained as the canonical file.
The project is not purely cosmetic. Storage costs on the council's hybrid cloud arrangement — split between local servers at the Portsmith technology facility and a managed cloud tier — have drawn scrutiny at a time when the organisation is also funding infrastructure for the Cairns Hospital campus expansion communications rollout and upgraded emergency alert systems for the Cape York corridor communities. Eliminating redundant files is expected to reduce annual managed storage expenditure, though council has not publicly confirmed a specific savings figure.
For residents, the most visible consequence of unresolved duplication has been outdated photographs appearing on high-traffic pages — including, in at least two documented cases in 2025, old aerial images of the Esplanade Lagoon precinct showing infrastructure that had since been modified. Those errors prompted formal complaints through council's customer request system.
The deduplication work is scheduled for completion before the end of the 2025–26 financial year, which closed on June 30. A post-implementation review is planned for the September 2026 quarter. Going forward, council's records and information management policy — last updated in March 2025 — requires all new image assets above a defined file-size threshold to be registered in a central digital asset register before publication, with a named staff member assigned as the responsible custodian for each asset batch. The intent is to prevent the same slow accumulation of orphaned files from occurring across the next platform cycle.
