Appearance
The International Image Interoperability Framework (IIIF, pronounced "triple-eye-eff") is a set of open REST APIs that let any compliant viewer display images and their descriptions from any compliant server, regardless of who built either side. In plain terms: it is a shared agreement so that a manuscript digitised in Oxford can be opened, zoomed, annotated and compared in a viewer hosted in Stanford without anyone exchanging files. It is a specification, not an application you download.
What problem does IIIF actually solve?
Before IIIF, every digital library shipped its own bespoke image viewer, its own URL scheme, and its own metadata format. A scholar comparing two manuscript leaves held in different libraries had to download JPEGs, screenshot, or beg for special exports. IIIF replaces that silo model with four small, stable contracts so that images become addressable, zoomable resources on the open web. The win is reuse: one digitisation effort, consumed by many tools and many institutions.
What are the core IIIF APIs?
There are four specifications, but two carry almost all the weight:
| API | Purpose | Returns |
|---|---|---|
| Image API | Deliver pixels on demand with crop, scale, rotate, quality | An image (JPEG, PNG, etc.) |
| Presentation API | Describe structure, order, and metadata of an object | JSON manifest |
| Content Search API | Search annotations and full text within an object | JSON results |
| Authentication API | Gate access to restricted material | Tokens and probe responses |
The Image API is the engine; the Presentation API is the table of contents that points at it.
How does the Image API request work?
The Image API encodes everything you want in the URL itself. The pattern is:
{scheme}://{server}/{prefix}/{identifier}/{region}/{size}/{rotation}/{quality}.{format}A concrete request for a 1024-pixel-wide version of the full image:
https://images.example.org/iiif/3/manuscript-12r/full/1024,/0/default.jpgChange full to 2000,1000,800,600 and you get a 800x600 crop starting at pixel (2000,1000). The viewer never downloads the whole 400-megapixel master; it asks only for the tiles it needs.
What is a IIIF manifest?
A manifest is a JSON document, served from a URL, that says "this object is made of these canvases, in this order, with this metadata, and the pixels live at those Image API endpoints." Drop a manifest URL into Mirador or the Universal Viewer and the object appears fully navigable. The manifest is the unit you share and cite, and it is the reason a single link can carry an entire digitised codex.
Do I really need IIIF for my project?
Be honest about scale. IIIF earns its complexity when you have very large images that demand deep zoom, when you want other institutions to embed or annotate your material, or when you are building cross-collection comparison tools. For a portfolio of 200 modest photographs with no reuse ambition, a static gallery is faster to ship. The framework rewards collections, not one-offs.
How do I start understanding IIIF hands-on?
The fastest way to build intuition is to inspect real manifests. Open any manifest URL from a major library, pretty-print the JSON, and trace how items (canvases) point to body resources on an Image API. Then load the same URL into a public viewer and watch how the JSON becomes an interface. Twenty minutes of this teaches more than any diagram.
Key Takeaways
- IIIF is a specification (a set of REST APIs), not software you install.
- The Image API serves pixels via URL parameters; the Presentation API packages them into a manifest.
- A manifest is a shareable, citable URL that any IIIF viewer can open.
- Interoperability means cross-institution reuse without exchanging files.
- IIIF pays off at scale, with huge images, or where reuse matters; small one-offs may not need it.
- Presentation API v3 extends the model to audio and video, not just images.
Frequently Asked Questions
What does IIIF stand for?
IIIF stands for the International Image Interoperability Framework. It is a set of open, community-maintained REST APIs that describe how to deliver images and the structured descriptions that surround them.
Is IIIF a piece of software I install?
No. IIIF is a specification, not a program. You implement it with software such as Cantaloupe or IIPImage on the server side and Mirador or Universal Viewer on the client side.
What are the main IIIF APIs?
The two foundational ones are the Image API, which serves pixels with region, size, rotation and quality parameters, and the Presentation API, which packages those images into a manifest with metadata and structure.
Do I need IIIF for a small collection of a few hundred images?
Often not. If images are small and you have no deep-zoom or cross-institution needs, static files in a viewer are simpler. IIIF pays off at scale, with very large images, or when you want others to reuse your content.
Can other institutions display my images if I publish IIIF?
Yes. Because manifests are URLs to standardised JSON, any IIIF-aware viewer can load your content directly, which is the whole point of interoperability.
Is IIIF only for images?
Originally yes, but the Presentation API version 3 also supports audio and video resources, so the same framework can describe time-based media.