What is IIIF, and why do museum image collections use it?

A collection image placed under an open license is reusable in theory the moment it is published. In practice, reuse still requires a usable file, a license a user can find, and a way to view the image without downloading an enormous master. IIIF, the International Image Interoperability Framework, is the technical standard that closes that gap, letting one institution serve an image that any compliant website can display, zoom, crop, and compare, without ever copying the file (https://iiif.io/about/).

What problem does IIIF actually solve?

Before shared standards, each museum's website had its own image viewer, its own zoom behavior, and its own way of serving a large file. A researcher comparing a manuscript page held by one institution with a related page held by another had to open two unrelated tools, each with different controls, resolutions, and licensing notices. IIIF defines a common application programming interface for requesting image regions, sizes, and rotations directly from the server that holds the file, so any IIIF-compliant viewer, built by any institution, can display any IIIF-compliant image the same way. The image stays on its home server; only the specific crop and resolution a viewer asks for is transmitted.

How does this change what "open access" actually delivers?

An open license answers the legal question of reuse. IIIF answers the practical one. A policy drafted around a Creative Commons license, the subject of open access policy decisions elsewhere on this site, states what a user may do with an image; IIIF is what lets them do it without friction, by giving them deep zoom on a high-resolution file, the ability to pull a specific detail as its own image request, and a stable, citable identifier for that exact view. A license without a usable delivery mechanism still leaves reuse to whoever has the technical resources to process a raw master file. IIIF lowers that bar for everyone.

Why have institutions coordinated around one shared standard?

IIIF is maintained by the IIIF Consortium, founded in 2015 and made up of universities, libraries, museums, archives and vendors that jointly govern the specification so no single institution's internal choices dictate how images are served elsewhere (https://iiif.io/community/consortium/). That governance model mirrors the earlier shift described in this archive's account of cataloguing standards: moving from locally invented systems to shared, portable rules that let institutions interoperate instead of each solving the same problem differently. A researcher who learns one IIIF viewer can use it against any participating collection, the same way a shared metadata standard let one cataloguing approach work across institutions rather than only within one building.

What does this mean for rights and attribution in practice?

IIIF does not replace a rights statement, it carries one. The manifest, the structured document an institution publishes to describe an object and its images, includes a required statement that must be displayed with the resource, a rights field pointing to a Creative Commons license or a RightsStatements.org statement, and a provider field naming the contributing institution (https://iiif.io/api/presentation/3.0/). That keeps the rights information attached to the image wherever it is displayed, rather than depending on a user to find and preserve a separate webpage's text. For anyone clearing rights before republishing a museum image, the manifest is a faster, more reliable place to check attribution requirements than the surrounding page, because it travels with the image itself.

What should an institution weigh before adopting it?

Serving images through IIIF requires an image server capable of generating tiles and regions on demand, not just a folder of static files, so adoption is an infrastructure decision as much as a policy one. The payoff is that a single published image becomes usable inside any IIIF-aware tool, from a university's research viewer to another museum's comparison platform, without the institution building or maintaining that tooling itself. For institutions weighing an open access policy, IIIF is frequently the deciding factor in whether "open" means a downloadable file or genuine, friction-free reuse across the web.

How should a researcher recognize and use a IIIF image?

Look for a manifest link, often labeled explicitly as IIIF, near a collection image, or a viewer with a visible zoom and pan interface distinct from a basic image lightbox. That manifest can usually be dropped directly into any compliant IIIF viewer elsewhere, independent of the institution that published it, which is the clearest practical sign that an image was built for reuse rather than only for display on its original page.