International Image Interoperability Framework

The International Image Interoperability Framework (IIIF, pronounced "triple-eye-eff") has fundamentally changed how cultural heritage institutions deliver digital objects on the web. By defining a suite of six open API specifications with three approved extensions, IIIF enables researchers, developers, and the public to access, compare, and annotate high-resolution images and audiovisual content across institutional boundaries. Backed by a consortium of leading libraries, museums, and archives, IIIF has grown from a focused image delivery protocol into a comprehensive framework for digital object interoperability.

Background

IIIF emerged in 2011 from conversations among staff at Stanford University, the British Library, the Bodleian Libraries at Oxford, the Bibliotheque nationale de France, and other institutions that were independently building similar image delivery infrastructure. Rather than duplicate effort, these organizations collaborated on shared API specifications. The first Image API (version 1.0) was published on August 10, 2012, enabling standardized requests for image regions, sizes, rotations, and quality levels. The Presentation API followed, providing a JSON-LD manifest format for structuring sequences of images with descriptive metadata. The IIIF Consortium was formally established in 2015 to sustain the community's governance, outreach, and technical development. Specifications follow a transparent editorial process with community review periods before promotion to stable status.

Purpose & Scope

IIIF addresses the persistent problem of images and audiovisual resources locked in institutional silos, accessible only through locally built viewers. The framework's six current APIs work together to provide a complete solution:

Approved Extensions

Three formally published extensions extend the Presentation API:

• navPlace Extension — defines geographic coordinates for resources using GeoJSON-LD
• Text Granularity Extension — indicates the level of text granularity for OCR, transcription, and digitized text annotations
• Georeference Extension — leverages Web Annotations to georeference Canvases and Image API resources

Serializations & Technical Formats

All IIIF API responses use JSON-LD as their serialization format, referencing IIIF-specific JSON-LD contexts. Image content is delivered via standard HTTP, with the Image API defining a URI syntax for requesting specific image derivatives. The framework does not prescribe a particular image storage format, though JPEG 2000 and pyramidal TIFF are commonly used for efficient tile-based delivery. Community translations of the specifications are available in Japanese and Chinese.

Governance & Maintenance

The IIIF Consortium manages governance through an elected Executive Committee drawn from member institutions. Technical work is organized into community groups and technical specification groups covering areas such as 3D, audiovisual content, maps, and museums. Specifications follow the IIIF Editorial Process on GitHub, with community review before versions are promoted to stable. The Consortium funds a small staff coordinating events, outreach, and infrastructure.

Validators

IIIF provides two official validators:

• Image API validator — validates IIIF Image API resources against the specification
• Presentation API validator — validates IIIF Presentation API resources against the specification

Notable Implementations

IIIF is deployed by major institutions worldwide, including the British Library, Library of Congress, Bibliotheque nationale de France, the Vatican Library, the Rijksmuseum, the Wellcome Collection, and the New York Public Library. Viewers such as Mirador, Universal Viewer, and Clover provide rich browsing, annotation, and comparison capabilities. Aggregators including Europeana and the Digital Public Library of America support IIIF for cross-collection discovery. Image servers like Cantaloupe, IIPImage, and Loris implement the Image API for tile-based delivery.

Related Standards

• JSON-LD — the serialization format for all IIIF API responses
• Web Annotation Data Model — the W3C standard used by IIIF for annotation
• Dublin Core — descriptive metadata vocabulary commonly referenced in IIIF manifests
• Schema.org — structured data vocabulary used alongside IIIF for discovery

Further Reading

• IIIF APIs & Documentation
• How IIIF Works
• IIIF Cookbook of Recipes
• Community Groups
• GitHub
• Wikipedia article