Appearance
To add IIIF to Omeka S you install the IIIF Server module so your installation can publish manifests, optionally pair it with an image server (Cantaloupe or the bundled Image Server module) for deep-zoom tiles, then add a Mirador or Universal Viewer module to display it. IIIF (the International Image Interoperability Framework) lets any compliant viewer open your images, and lets you embed other institutions' images without copying them. For large images and manuscripts the payoff is fast, zoomable, shareable views.
What does IIIF give an Omeka S collection?
Without IIIF, Omeka serves a fixed-size derivative and a single full image. With IIIF, each image becomes a tile service: viewers request only the region and resolution on screen, so a 400-megapixel manuscript scan opens instantly and zooms smoothly. You also get manifests, small JSON documents that describe an object's pages and metadata, which any IIIF viewer anywhere can load. That is the interoperability win.
Which modules do you actually install?
A typical stack:
- IIIF Server — exposes the Image and Presentation APIs from Omeka and builds manifests.
- Image Server (Cantaloupe-backed) — generates deep-zoom tiles from your masters.
- Mirador or Universal Viewer — the front-end viewer module.
Install each by unzipping into modules/ and activating it:
bash
cd /var/www/html/omeka-s/modules
unzip IiifServer.zip
unzip ImageServer.zip
unzip Mirador.zipThen go to Modules in the admin and click Install on each.
How do you embed someone else's IIIF image?
This is the gentlest place to start because it needs no image server at all. When adding media to an item, choose media type IIIF and paste a remote image-service or manifest URL:
text
https://iiif.bodleian.ox.ac.uk/iiif/image/<id>/info.jsonOmeka stores the reference, not the pixels. Your item now displays a remote, zoomable image you do not host. This is ideal for teaching collections that point at digitised originals elsewhere.
How do you publish your own images as IIIF?
Upload a high-resolution master to the item as normal. With the IIIF Server and Image Server modules active, Omeka exposes a manifest at a predictable URL:
text
https://your-omeka/iiif/3/<item-id>/manifestOpen that URL in any external Mirador instance and your object loads, proving interoperability. On your own site, the Mirador module renders it inline on the item page.
Which viewer should a beginner choose?
| Viewer | Best for | Note |
|---|---|---|
| Mirador | Comparing two or more objects side by side | Researcher-oriented |
| Universal Viewer | Single-object linear reading, books | Reader-oriented |
If your collection is manuscripts visitors flip through, Universal Viewer feels natural. If scholars compare leaves across objects, Mirador wins. You can install both and choose per site.
What are the common first-time mistakes?
- Activating the IIIF Server but no image server, then wondering why deep-zoom is missing.
- Uploading small derivatives instead of high-resolution masters, so there is nothing to zoom into.
- Forgetting CORS: external viewers loading your manifest need permissive CORS headers, or they fail silently.
- Treating IIIF as mandatory for tiny images, adding complexity with no benefit.
Key Takeaways
- IIIF turns each image into a zoomable tile service plus a portable JSON manifest.
- Install IIIF Server for manifests, an image server for tiles, and a viewer module to display.
- You can embed remote IIIF images by reference without re-hosting any pixels.
- Mirador suits comparison; Universal Viewer suits linear reading.
- Upload high-resolution masters and set permissive CORS so external viewers work.
- Skip IIIF for a handful of small images; it pays off at scale and for manuscripts.
Frequently Asked Questions
Which module adds IIIF to Omeka S?
The IIIF Server module exposes Image and Presentation APIs from your Omeka S installation, and the Image Server (Cantaloupe-backed) module or an external IIIF image server provides deep-zoom tiles.
Do I need a separate image server, or does Omeka do it all?
The IIIF Server module can generate basic manifests, but for true deep-zoom of large images you pair it with an image server such as Cantaloupe or use the bundled Image Server module.
Can I display images from another institution's IIIF in Omeka S?
Yes. Add media of type 'IIIF' and paste the remote manifest or image-service URL. Omeka stores the reference rather than copying the pixels, so you embed without re-hosting.
What viewer does Omeka S use for IIIF?
Mirador and the Universal Viewer are both available as modules. Mirador suits side-by-side comparison; Universal Viewer suits a single linear reading experience.
Will IIIF slow my site down?
No, usually the opposite. Visitors load only the tiles they view rather than full multi-megapixel masters, so large images feel faster than a single huge JPEG.
Is IIIF overkill for a few small images?
Often yes. For a handful of small photographs, normal Omeka media is simpler. IIIF pays off with large images, manuscripts, or when you want cross-institution reuse.