From Folder to Manifest in a Minute: Introducing tiny.iiif

February 03, 2026

Today’s post is a bit of a guest appearance. It’s not actually about liiive at all, but instead about another small project of mine: tiny.iiif.

If you ever had a folder of image files and asked yourself how you can turn them into a working IIIF Presentation manifest–without setting up a full-blown collection management system–this post is for you.

Screenshot of the tiny.iiif admin GUI

Using IIIF resources online is becoming easier all the time, thanks to a growing ecosystem of viewers, tools and software libraries. But every now and then I get asked about options for publishing your own images as IIIF. I always felt there’s a bit of a gap there.

On the one hand, IIIF is a standard that’s predominantly implemented by larger institutions. So it’s not surprising that lightweight publishing workflows for small, personal collections aren’t really a thing. In an institutional setting, IIIF is usually just a feature of a larger asset management system.

On the other hand, there are plenty of situations where you might want to publish a very small collection–maybe a few dozen images: for classroom work, a small exhibition, or to present results of a thesis or research project.

Hosting Your Own IIIF Collection

The (awesome!) awesome-iiif list includes several hosting options for publishing images as IIIF. In practice, though, these options aren’t always easy to get started with, can be costly, or only provide an Image API endpoint.

One of the more approachable alternatives is Omeka-S, which is an excellent digital collection platform with IIIF support. But it still comes with a learning curve, and it may be overkill if all you have is a bunch of folders of JPEGs and all you want is to see those folders online as manifests.

tiny.iiif

tiny.iiif is meant to fill exactly this gap. It’s a minimal open-source IIIF server, built specifically for cases where you just want to turn a bunch of images into a functional IIIF collection with as little friction as possible.

It provides:

The goal isn’t to replace a collection platform, but to offer a middle ground between full asset management system and hand-editing your own manifest JSON.

Technical Overview

Under the hood, tiny.iiif combines three components:

Everything is packaged using Docker Compose, so there’s no need to install or configure these pieces manually. In a typical setup, getting started is mostly a matter of setting the admin username and password and launching the stack with a single Docker Compose command.

Important: this also means tiny.iiif is self-hosted server software. You will need access to a server (physical or virtual) and be reasonably comfortable with basic server administration and Docker. If that’s within your comfort zone, tiny.iiif should get you from images-on-disk to published IIIF resources very quickly.

Update: if you like the idea of tiny.iiif but don’t want to deal with running your own server, I’m now also starting to offer a managed hosting service – see last paragraph of this blogpost!

Using the Admin Interface

The part that’s actually new about tiny.iiif is the admin GUI:

From there:

In other words: folders become manifests, without any additional configuration.

Try It Out

If you’d like to give it a try, the code and setup instructions are available on GitHub:

https://github.com/rsimon/tiny-iiif

tiny.iiif is MIT licensed and still evolving. Contributions are welcome and I’d love to hear your feedback!

Update: Managed Hosting

If you would like to use tiny.iiif but don’t want to set up and maintain your own server, I can host it for you. You’ll get your own private tiny.iiif instance at a custom address of your choice:

https://your-name.tiny-iiif.org

Managed hosting is available for a modest fee, which directly supports the continued development of the project. If this sounds useful, drop me a short email and I’ll put together an offer that fits your needs.

Rainer

Hi I'm Rainer, a freelance software developer based in Vienna, Austria. I created liiive out of a passion for the Digital Humanities and a fascination with realtime web technologies. I believe that studying historical materials online should feel as natural and engaging as gathering around a table together. For updates and tips, follow me on Mastodon or Bluesky.