Open-source digital collections in 2026 (Omeka S)

Digital collections are how museums, libraries, and archives put their holdings in front of the public. The software that runs them has quietly turned into a recurring bill, and for many teams the bill keeps climbing while the collection stays inside a vendor's account. Omeka S is the open-source way out — a publishing platform built for galleries, libraries, archives, and museums (GLAM) and digital humanities, run on infrastructure you control.

This is a narrow piece for a narrow audience. If you publish structured collections with real metadata, read on. If you want a marketing website, this is the wrong tool, and the post says so plainly.

The short version

• Omeka S publishes digital collections, items, and exhibits with linked metadata. It was built for GLAM and digital humanities, not as a general website builder.
• CONTENTdm is sold by quote and renews in the thousands per year. Hosted Omeka.net runs only Omeka Classic, priced from $35 to $1,000 a year by storage tier.
• Managed Omeka S at DANIAN is €9 per month, with 30 GB of storage included and the region you choose.
• Media-heavy collections pass 30 GB fast. Storage, not the base fee, is the first number to estimate.
• For a tiny Omeka Classic exhibit under a few gigabytes, Omeka.net's cheap tiers still win on price. The post names where each path fits.

Why teams leave hosted collections SaaS in 2026

Two costs push GLAM teams to look elsewhere: the invoice and the loss of control. CONTENTdm is quoted per institution and renews in the thousands per year. Hosted Omeka.net runs only Omeka Classic and caps storage by tier. Both put your collection, its metadata, and its uptime inside someone else's product.

Start with the money. CONTENTdm pricing is not published; OCLC quotes each institution. A documented small-tier order ran about $11,782 in the first year and roughly $3,372 a year after that, against a 40 GB hosting limit. Those are 2014 figures, and current pricing is quote-only, so treat them as an order of magnitude. The free "quick start" tier caps at 100 items and is offered in the Americas only.

Omeka.net publishes five tiers: Free at 500 MB, Plus at $35 a year for 2 GB, Silver at $75 for 5 GB, Gold at $350 for 10 GB, and Platinum at $1,000 for 50 GB. Every tier runs Omeka Classic, not Omeka S, and storage is fixed by plan. For a small exhibit that is fine. For an institutional collection that needs the newer platform, it is a ceiling.

Then the control. On a hosted plan your items, media, and metadata sit on the vendor's servers under the vendor's terms. Export exists, but the live site, the URL, and the upgrade cycle belong to the host. For a collection meant to outlive a grant, that dependency is the real risk. Budgets are tighter this year, grant reporting wants durable public access, and teams are reviewing every recurring line of software spend.

What "alternative" means for digital collections

The alternative here is not a cheaper SaaS. It is the open-source platform the SaaS was built to resemble, run on infrastructure you control. For digital collections that platform is Omeka S, with Omeka Classic as the lighter sibling. You keep the standards-based metadata and gain ownership of the stack underneath it.

Three paths exist. Stay on a hosted collections SaaS and pay the per-tier or quoted fee. Self-host Omeka S on a server you run. Or have a managed host run Omeka S for you at a flat monthly rate. The last two paths run the same open-source code; what differs is who patches the server.

One caution up front. Omeka S is not a general website builder. It does not replace WordPress or Drupal for editorial or marketing sites. It models collections: items, media, and metadata described with controlled vocabularies and published as linked data. If your goal is a brochure site, this is the wrong fit. If your goal is a structured, searchable, durable collection, it is the right one.

The shortlist

Three open-source tools cover the digital-collections workflow. One publishes, one is its lighter sibling, and one holds your source files.

Omeka S — the institutional publishing platform

Omeka S publishes digital collections, items, and media-rich exhibits from one install that can run many sites. It is built around Linked Open Data, with JSON-LD as its native format and Dublin Core resource templates for describing records. It was built by the non-profit Corporation for Digital Scholarship and first released in 2017. GPL-3.0 licensed, 493 GitHub stars. Managed at DANIAN for €9 per month. Best for institutions running structured collections across one or several sites.

Its strength is the module system. IIIF Server and viewers such as Mirador and the Universal Viewer add deep-zoom for high-resolution images. CSV and bulk-import modules move metadata in from a spreadsheet or another system. Mapping and timeline modules add context. These extend the core without touching the codebase, which keeps upgrades clean.

Omeka Classic — the single-site sibling

Omeka Classic is the original single-site version, first released in 2008 and downloaded more than 500,000 times. It suits a focused exhibit or a small collection under one theme, with Dublin Core and the same access-focused design. GPL-3.0 licensed. It is the platform the hosted Omeka.net service runs. If you only need one small exhibit, Classic on a low Omeka.net tier is a fair, cheap path and worth considering before anything heavier.

Nextcloud — a controlled home for source files

Nextcloud is open-source file sync and storage. In a collections workflow it holds the master files — the full-resolution TIFFs, audio, and video — that you do not want to serve from the public site. You publish access derivatives through Omeka S and keep the masters in Nextcloud. Managed at DANIAN for €9 per month. Best for teams that need a private, controlled store for large source assets. See Nextcloud for source files.

See managed Omeka S hosting.

What a collection looks like in Omeka S

Omeka S has three building blocks: items, item sets, and sites. An item is one record — a photograph, a letter, an oral history. An item set groups related items into a collection. A site is the public face, with pages, browsing, and exhibits built from those items. Metadata ties the three together.

Start with an item. Say you are digitising a 1923 letter. The item holds the scanned image as attached media, plus a set of fields: title, creator, date, subject, rights. Omeka S describes those fields with Dublin Core by default, so "creator" and "date" mean what they mean in every other standards-based system. A resource template fixes which fields a letter should carry, so every letter in the collection is described the same way.

Linked data is the part a hosted SaaS rarely gives you. Each value can be plain text or a link to an authority — a Library of Congress subject heading, a Getty vocabulary term, a Wikidata entity. "Paris, France" stops being loose text and becomes a stable identifier that other systems can follow. That is what linked metadata means in practice, and it ships in the core, not as a paid tier.

An exhibit is the narrative layer. You arrange selected items into pages with text, captions, and a reading order — a curated path through the collection rather than a flat list. Visitors get a story; the items stay reusable. One letter can appear in a teaching exhibit, a public exhibit, and a research index without being copied for each.

What it costs versus CONTENTdm and Omeka.net

For a 10 GB collection, Omeka.net Gold is $350 a year and runs Omeka Classic; managed Omeka S at DANIAN is €108 a year with 30 GB included. At 50 GB the gap widens: Omeka.net Platinum is $1,000 a year, while DANIAN is about €228 a year. CONTENTdm sits well above both, whichever way you convert currencies.

The self-host row needs unpacking. A $24-a-month production-class VPS, plus about $5 for off-site backup and $15 for monitoring, is roughly $44 a month before your own time. Patching PHP and MySQL, processing images, and verifying backups take one to two hours a month. At freelance rates that is €60 to €240 a month in time. The code is free; the operations are not.

Where the SaaS still wins. If you only need a single small Omeka Classic exhibit under a few gigabytes, Omeka.net's Plus and Silver tiers, at $35 and $75 a year, are cheaper than €108 and need no setup. If your library lives inside OCLC's ecosystem — WorldCat Discovery and shared cataloging — CONTENTdm's sync into WorldCat is something a self-run Omeka S site does not replicate. Price is not the only axis. Name what you actually need before you switch.

Where managed Omeka S wins. You get Omeka S itself, not Classic. You pick the region your collection sits in. Patching, daily off-site backups, and monitoring are included in the €9, with no per-item fee and no per-seat fee. The one number that scales is storage, which is the next section.

The storage question for media-heavy collections

Digital collections are heavy. A single archival TIFF can run 50 to 200 MB; audio and video run larger. DANIAN includes 30 GB per app and charges €0.50 per GB per month beyond that. Estimate your gigabytes before assuming €9 covers everything — for large master archives, storage is the cost that matters, not the base fee.

Do the math first. A collection of 5,000 access images at 2 MB each is about 10 GB, comfortably inside the included 30 GB. The same 5,000 images as 100 MB master TIFFs is 500 GB, which is 470 GB of overage at €0.50, or about €235 a month on top of the €9. The base fee did not change; the master files did.

The fix is standard practice in the field. Serve access derivatives — web-sized JPEGs and IIIF tiles — from Omeka S. Keep the full-resolution masters in cold storage or in Nextcloud, not on the public site. That keeps the live collection light and the public experience fast, and it mirrors how most institutions structure preservation anyway. See Nextcloud for source files.

How to pick: three questions

Three questions sort most teams. They are about the version you need, the files you hold, and the time you have. Answer them honestly and the path is usually obvious. The decision comes down to cost and the staff hours you can spare.

1. Do you need Omeka S, or is Classic enough? Multi-site, linked data, and resource templates mean Omeka S. A single small exhibit means Classic, and a cheap Omeka.net tier may be all you need.
2. How large is your media library? Under 30 GB of access files fits the included storage. Hundreds of gigabytes of masters means you plan storage first and keep masters off the public site.
3. Who patches the server? If you have in-house staff who run PHP and MySQL, self-hosting on a production-class VPS is a real path. If you do not, a managed host runs it for roughly the cost of the time you would otherwise spend.

Frequently asked questions

Omeka S basics and fit

What is Omeka S?
Omeka S is an open-source platform for publishing digital collections, items, and exhibits with structured, linked metadata. It was built by the non-profit Corporation for Digital Scholarship for museums, libraries, archives, and digital humanities work. It is GPL-3.0 licensed and runs one or many sites from a single install.

How is Omeka S different from Omeka Classic?
Omeka S runs many sites from one backend and is built around Linked Open Data, with resource templates and controlled vocabularies. Omeka Classic is the original single-site version from 2008, better for a focused exhibit. The hosted Omeka.net service runs Classic, not Omeka S.

Is Omeka S an alternative to CONTENTdm?
Yes, for many collections. Omeka S publishes items, media, and exhibits with standards-based metadata, the core of what CONTENTdm does. CONTENTdm adds WorldCat sync and OCLC's hosted support, which matter most to libraries inside the OCLC ecosystem. For teams that want ownership and flat cost, Omeka S fits.

Is Omeka S a general website builder like WordPress?
No. Omeka S models collections — items, media, and metadata described with controlled vocabularies and linked data. It does not replace WordPress or Drupal for editorial or marketing sites. If you need a brochure site, pick a general CMS. If you need a structured, searchable collection, pick Omeka S.

What metadata standards does Omeka S use?
Omeka S uses Dublin Core by default and lets you add other vocabularies through resource templates. Its native data format is JSON-LD, so records publish as Linked Open Data. Modules add IIIF deep-zoom image support and viewers, keeping your collection interoperable with other systems and repositories.

Migration and data ownership

Can I move my collection off CONTENTdm or Omeka.net?
Yes. CONTENTdm exports metadata to XML and tab-delimited formats, and Omeka.net offers a site export. You import into Omeka S using its CSV and bulk-import modules, mapping fields to Dublin Core. Plan staff time for cleanup; migration is mechanical but rewards careful field mapping.

Do I own my data and metadata on managed Omeka S?
Yes. The Omeka S install, its database, and your files run on infrastructure you control, not inside a vendor's collections product. You can export records and media at any time. Managed hosting runs the server; the collection and its metadata stay yours to move or keep.

Can I export everything if I leave?
Yes. Omeka S stores items and media in a standard MySQL database with files on disk, and records export as JSON-LD or CSV. There is no proprietary wrapper around your collection. Leaving means taking a database dump and your files — no per-record lock-in and no exit fee.

Will my collection survive after a grant ends?
That is a core reason teams pick open source. Because Omeka S is GPL-3.0 and the data is portable, the collection does not depend on a vendor staying in business or a subscription staying funded. On managed hosting you keep the site running for a flat fee; on your own server, you keep the code.

Cost and storage

How much does managed Omeka S cost?
Managed Omeka S at DANIAN is €9 per month, which is €108 a year. That covers patching, daily off-site backups, monitoring, and 30 GB of storage, in the region you choose. There is no per-item fee and no per-seat fee. Storage beyond 30 GB is €0.50 per GB per month.

Is Omeka S cheaper than Omeka.net or CONTENTdm?
Usually, with one exception. CONTENTdm renews in the thousands per year; Omeka.net Gold is $350 and Platinum is $1,000. Managed Omeka S is €108 a year. The exception: a tiny Omeka Classic exhibit under a few gigabytes is cheaper on Omeka.net's $35 to $75 tiers.

How much storage do digital collections need?
More than teams expect. A single archival TIFF can run 50 to 200 MB; audio and video run larger. Five thousand 2 MB access images is about 10 GB, inside the included 30 GB. The same images as master TIFFs can reach 500 GB, so estimate your gigabytes early.

What happens if my collection grows past 30 GB?
Storage beyond the included 30 GB is €0.50 per GB per month. A 200 GB collection is 170 GB of overage, about €85 a month on top of the €9. The fix most institutions use is serving web-sized access images from Omeka S and keeping master files in separate storage.

Are there bandwidth or traffic charges?
DANIAN includes 1,000 GB of bandwidth per month, then charges €0.03 per GB beyond that. For most collections, normal public browsing stays well inside that allowance. Heavy spikes — a viral exhibit or large media downloads — are where bandwidth becomes a line item worth watching.

Running it: managed or self-hosted

Should I self-host Omeka S or use managed hosting?
Self-host if you have staff who run PHP and MySQL and enjoy it; a production-class VPS plus backup and monitoring is about $44 a month before your time. Choose managed hosting if you would rather not patch servers — the flat €9 covers the work you would otherwise do yourself.

What does managed hosting actually handle?
Managed Omeka S includes server patching, daily off-site backups, monitoring, and support over chat or email with a person who replies. You manage your collection — items, metadata, exhibits, and users — from the Omeka S admin. The infrastructure underneath is run for you, so you are not on call.

Where is my collection hosted, and can I choose?
You choose the region, from 21 datacenter locations across six continents. Pick the one closest to your visitors or your institution. Application data for your collection sits in the region you select, so you are not pinned to a single default location chosen for you.

Is my collection isolated from other customers?
Yes. Each app runs in its own hardened, isolated container with its own database and storage, not in a shared pool. Your Omeka S install does not share its application space with another customer's. Backups are stored off-site, kept separate from the running instance.

What to do this week

Pick the smallest real step. Estimate your storage, export a sample of your metadata, and stand up one Omeka S site to test the migration. You will learn more from one live collection than from another month of comparison.

Start with a 7-day trial of managed Omeka S and import a single collection. Map your Dublin Core fields, load a handful of items, and see how the linked-data templates fit your records. Start a 7-day trial.

Keep your master files in a separate, controlled store from day one. Publish access derivatives, not masters. That one decision keeps both your costs and your public site under control as the collection grows.