Libraries have always been in the business of preservation and access — collecting knowledge, organizing it carefully, and making it available to the people who need it. The format of that knowledge has changed dramatically over the past two decades. Where once the challenge was cataloging physical volumes and maintaining reading rooms, today librarians also manage digitized special collections, online catalogs, born-digital archives, streaming media, research databases, and public-facing websites that serve patrons around the clock.

At the heart of all of it — often invisible, rarely discussed — is web hosting.

The decisions a library or digital archive makes about its hosting infrastructure affect everything from how quickly a patron can search the catalog to whether a century-old photograph in a digitized collection remains accessible in thirty years. Those aren’t small decisions. And yet many libraries are making them without a clear framework, working around outdated infrastructure, or relying on institutional IT departments that weren’t specifically designed to serve the unique needs of library and archival work.

This guide is written specifically for librarians, archivists, and library administrators. We’ll translate the technical world of web hosting into language that connects to what you already know — collection management, preservation principles, access and discovery, patron service — and give you a practical foundation for making better decisions about your digital infrastructure.

1. The Digital Library’s Unique Hosting Needs

Most web hosting guides are written for businesses selling products or individuals building personal websites. Libraries and digital archives have a fundamentally different set of priorities — and those differences should drive every hosting decision you make.

Access Over Everything

The core mission of a library is access. Whatever you’ve collected, organized, and preserved means nothing if patrons can’t reach it. For a physical library, access means open doors and staffed reference desks. For a digital library, access means a website that loads reliably, a catalog that returns accurate results quickly, and digitized collections that are available to researchers at any hour from any location.

Unlike a business website where brief downtime is an inconvenience, a library website that goes down during finals week, during a research deadline, or while a remote patron is mid-session in a special collection represents a genuine failure of institutional mission.

Long-Term Thinking vs. Short-Term Cycles

Businesses think in quarters. Libraries think in decades — sometimes centuries. A digitized newspaper archive created today needs to still be accessible and properly formatted in 2045. A born-digital special collection donated to your institution this year needs a hosting strategy that outlasts the technology used to create it.

This long-term orientation fundamentally changes how libraries should think about hosting. Choosing a provider based purely on the cheapest current price without considering stability, migration paths, and data portability is a decision that creates future problems at institutional scale.

The Diversity of Library Web Presences

No two library digital presences look exactly alike. Depending on your institution’s size, type, and mission, your web infrastructure might need to support:

Each of these has overlapping but distinct hosting requirements. A one-size-fits-all approach doesn’t serve any of them particularly well. Understanding your institution’s specific profile is the essential first step before evaluating any hosting solution.

2. Web Hosting Explained for Librarians

Before evaluating options, it’s worth making sure the foundational concept is clear — because hosting providers use a lot of jargon that can make a straightforward idea seem more complicated than it is.

Web hosting is the service of storing your website’s files on a powerful, always-connected computer called a server. When a patron types your library’s web address into their browser, or when a researcher searches your digital archive from across the country, their browser contacts your hosting server, retrieves the appropriate files, and displays them on screen. Without a hosting server, your digital presence has nowhere to live.

Think of it like the difference between a manuscript stored in a climate-controlled vault versus one that’s been digitized and made available online. The digitized version is the content. Hosting is the infrastructure — the servers, network connections, and software — that makes that content accessible to anyone with an internet connection, at any time, without requiring them to visit the physical building.

Key Infrastructure Components

A library’s web infrastructure typically consists of several interconnected components:

• Web hosting server — where your website’s files, databases, and media assets live
• Domain name — your web address (like citylib.org or specialcollections.university.edu)
• Content Management System (CMS) — the software your staff uses to update content without writing code
• Database server — stores your catalog records, patron data, and digital collection metadata
• File storage — where large digital assets like high-resolution scans, audio files, and video are stored
• CDN (Content Delivery Network) — optional but valuable; distributes your content across servers worldwide for faster delivery to remote users

3. Choosing Your Hosting Type

The hosting market offers a range of service tiers. Here’s how each one maps to the realities of library and archival work.

Shared Hosting — Limited Use Cases for Libraries

On shared hosting, your website shares a server with many other websites. It’s inexpensive at $3–$10/month but offers limited performance, storage, and control. For most libraries, shared hosting is insufficient as a primary solution — library websites typically involve databases, search functionality, and media delivery that shared hosting handles poorly under any meaningful traffic load.

Where shared hosting is appropriate for libraries: a small branch or friends-of-the-library group running a simple informational page with no catalog integration, no media delivery, and minimal traffic.

VPS Hosting — The Right Foundation for Most Libraries

A Virtual Private Server gives your library its own dedicated allocation of server resources within a shared physical machine. Your CPU, memory, and storage are reserved — other sites on the same machine can’t affect your performance. Typically $20–$80/month.

VPS hosting is the appropriate minimum standard for any library running a catalog interface, digital collection portal, or patron-facing services. It handles traffic spikes gracefully — when a local news story drives sudden interest in a digitized historical collection, or when the start of the school year brings a surge of student researchers, a VPS won’t buckle under the load the way shared hosting would.

Cloud Hosting — Best for Large Collections and Variable Traffic

Cloud hosting distributes your infrastructure across multiple servers. It scales automatically to meet demand and eliminates single points of failure — if one server has a problem, others immediately compensate. For large academic libraries hosting substantial digital collections, or for digital archives with unpredictable traffic patterns driven by research interest, cloud hosting provides the reliability and scalability that VPS alone may not.

Major cloud platforms used in library contexts include Amazon Web Services (AWS), Google Cloud Platform, and Microsoft Azure — all of which have specific products designed for large-scale digital asset storage and delivery. Costs vary based on usage, typically starting around $20–$150+/month for library-scale implementations.

Managed WordPress Hosting — For Public-Facing Library Websites

Many libraries separate their public-facing website (events, hours, news, staff directory) from their catalog and digital collection systems. For the public-facing site, managed WordPress hosting — where the provider handles all technical maintenance — is an excellent fit. It requires minimal technical overhead, performs well, and allows library staff to update content without IT involvement. Typically $20–$60/month.

Institutional and Consortium Hosting — A Library-Specific Option

Many libraries have access to hosting solutions through their institution (a university’s IT infrastructure), their state library agency, or a library consortium. These arrangements often offer favorable pricing, shared technical expertise, and hosting environments specifically configured for library software like Koha, Evergreen, or DSpace. If your library is part of a consortium or connected to a parent institution, exploring these options before going directly to commercial providers is worth the conversation.

4. Digital Preservation and Long-Term Access

This is the section that distinguishes a library hosting guide from every other hosting guide on the internet — and it’s the area where the stakes are highest for your institution.

Preservation Is Not the Same as Backup

This is one of the most important distinctions in digital library work. A backup is a copy of your current data, made for disaster recovery purposes. If your server fails today, a backup lets you restore what you had. That’s essential — but it’s not preservation.

Digital preservation is the set of practices that ensure digital content remains accessible, authentic, and usable over the long term — through hardware obsolescence, software format changes, organizational transitions, and the general entropy of digital infrastructure. Preservation requires active management, not just passive copying.

Key preservation practices that have hosting implications:

• Format migration — periodically converting digital files to current, widely-supported formats to prevent obsolescence (a TIFF scanned in 2005 is still accessible; a proprietary format from an early digital camera may not be)
• Multiple copies in geographically distributed locations — the digital preservation community’s standard is the 3-2-1 rule: three copies, on two different media types, with one stored offsite
• Fixity checking — regularly verifying that files haven’t been corrupted or altered since they were deposited, using checksums
• Persistent URLs — ensuring that the web addresses used to access collection items remain stable over time, even as underlying systems change

Persistent Identifiers and Stable URLs

When a researcher cites a digitized item from your collection in a published article, or when another institution links to a document in your archive, that URL needs to remain valid indefinitely. A hosting migration or system upgrade that breaks URLs is a preservation failure — and it damages your institution’s reputation as a reliable access point for scholarship.

Best practices for URL stability in library hosting:

• Use a persistent identifier system like DOI, Handle, or ARK (Archival Resource Key) for collection items
• Implement URL redirects whenever restructuring your site to preserve legacy links
• Document your URL structure and avoid hosting migrations that require changing item-level URLs without redirect mapping
• Consider using a resolver service that decouples the identifier from the hosting location — making future migrations much cleaner

The LOCKSS and Trusted Digital Repository Frameworks

For academic libraries and digital archives with serious preservation mandates, it’s worth knowing about established frameworks:

• LOCKSS (Lots of Copies Keeps Stuff Safe) — a distributed digital preservation network where participating libraries maintain copies of each other’s content
• ISO 16363 / TRAC — the Trustworthy Repositories Audit & Certification framework, used to formally assess and certify digital repositories
• NDSA Levels of Digital Preservation — a tiered framework from the National Digital Stewardship Alliance that provides a practical roadmap for improving preservation practices

Your hosting choices should be compatible with whatever preservation framework your institution uses or aspires to.

5. Metadata, Discovery, and SEO for Collections

Libraries are metadata experts. The same principles that make a physical catalog navigable apply to digital collections — but online, good metadata also drives discoverability through search engines, which is increasingly how researchers and patrons first encounter library resources.

Structured Data and Schema Markup

Search engines like Google can understand the content of your digital collections much better when you use structured data markup — specifically, Schema.org vocabularies embedded in your HTML. For libraries, relevant Schema types include:

• Book and Article — for digitized texts and publications
• ArchiveComponent and Collection — for archival materials
• ImageObject and VideoObject — for digitized photographs and audiovisual materials
• Library — for your institution’s main page, with hours, location, and services

Implementing structured data helps search engines surface individual items from your collections in search results — not just your homepage — which dramatically increases the discoverability of your holdings.

OAI-PMH and Metadata Harvesting

The OAI-PMH (Open Archives Initiative Protocol for Metadata Harvesting) is a standard used by digital libraries and archives to share metadata with aggregators like DPLA (Digital Public Library of America), Europeana, and institutional discovery systems. If your hosting and collection management system supports OAI-PMH, your metadata can be harvested and included in these larger discovery networks — making your collections visible to researchers who may never visit your site directly.

Ensure your hosting environment supports the OAI-PMH endpoint your digital collection platform requires, and that server configuration doesn’t block the automated metadata harvesting requests these aggregators send.

IIIF for Image-Based Collections

The IIIF (International Image Interoperability Framework) is a set of open standards that allows high-resolution images to be shared, zoomed, compared, and annotated across different institutions’ platforms. Major digital archives use IIIF to make their image collections interoperable — a researcher can compare a manuscript from your collection with related materials at a different institution, side by side, without downloading anything.

Hosting a IIIF-compliant image server (like Cantaloupe, IIPImage, or Loris) requires a server environment with sufficient processing power and bandwidth to deliver deep zoom tiles on demand. This is a hosting consideration that needs to be factored into your infrastructure plan if IIIF compatibility is a goal.

6. Hosting for Integrated Library Systems

An Integrated Library System (ILS) — or its more modern equivalent, a Library Services Platform (LSP) — is the software backbone of library operations: cataloging, circulation, acquisitions, serials management, and the patron-facing OPAC (Online Public Access Catalog). How this system is hosted has significant implications for performance, cost, and institutional control.

Cloud-Hosted vs. Locally Hosted ILS

The ILS hosting decision is one of the most consequential infrastructure choices a library makes. Two broad models exist:

Cloud-Hosted (Software as a Service)

The vendor hosts and maintains the system entirely. Examples include OCLC’s WorldShare Management Services, Ex Libris Alma, and the cloud version of Koha offered by various vendors. The library accesses everything through a web browser; the vendor handles servers, updates, security, and backups.

• Lower IT burden for the library
• Automatic updates and vendor-managed security
• Predictable subscription pricing
• Less control over customization and data portability
• Ongoing subscription cost; no perpetual license

Self-Hosted (On-Premises or Library-Managed VPS)

The library manages its own server infrastructure, running open-source systems like Koha or Evergreen. Full control over configuration, data, and customization — but also full responsibility for maintenance, security, and updates.

• Complete control over data and system configuration
• Lower long-term cost for libraries with technical capacity
• Requires IT staff or a managed service provider
• Hosting costs are the library’s responsibility

Open-Source ILS on Your Own Hosting

Libraries choosing to self-host open-source systems like Koha or Evergreen need a hosting environment configured for their requirements. Key specifications:

• A VPS with at least 4GB RAM for a small to mid-size library running Koha; 8GB+ for larger collections or high-circulation systems
• SSD storage for database performance — catalog search speed is directly affected by disk I/O speed
• A hosting provider comfortable with Linux server environments (Koha runs on Debian/Ubuntu)
• Regular automated backups of the database and configuration files
• SSL configured for the OPAC and staff client

7. Accessibility, Compliance, and the Law

Libraries have a deep institutional commitment to equitable access — and that commitment extends to the digital environment. It also, in many cases, carries legal weight.

ADA and Section 508 Compliance

The Americans with Disabilities Act (ADA) and Section 508 of the Rehabilitation Act require that public-sector websites and any digital resources funded by federal money be accessible to people with disabilities. For public libraries — which are government entities — and for academic libraries at federally-funded institutions, web accessibility is a legal requirement, not merely a best practice.

Practically, this means your website and digital collections must meet the WCAG 2.1 AA (Web Content Accessibility Guidelines) standard. Hosting implications include:

• Your CMS and themes must support accessible HTML output — not all WordPress themes are equally accessible
• Your server must deliver pages fast enough that screen readers and assistive technologies can interact with content without timing out
• Media files (audio, video) must be hostable in formats that support captions and transcripts
• PDF documents in digital collections should be processed for accessibility where possible

Privacy Laws and Patron Confidentiality

Library patron privacy is not just an ethical principle — it’s codified in professional standards (the ALA’s Code of Ethics) and in many states’ library confidentiality laws. What patrons read, search for, and access through your library is protected information. Your hosting environment and digital systems must reflect this commitment:

• Minimize data collection — don’t use analytics tools or advertising trackers that collect patron browsing data beyond what is operationally necessary
• Use privacy-respecting analytics — consider Matomo (self-hosted, privacy-friendly) over Google Analytics, which collects data that could compromise patron privacy
• SSL everywhere — all patron interactions with your website, catalog, and digital resources must be encrypted
• Limit log retention — server access logs that record patron IP addresses and browsing behavior should be retained only as long as operationally necessary, consistent with your library’s privacy policy

Copyright and Digital Collections

Your hosting decisions intersect with copyright law in ways that require careful attention. Digitized collections may contain materials under copyright. Access restrictions — password-protected pages for materials available only to library cardholders or affiliated researchers, geo-restrictions for licensed content, and robust rights metadata — all have technical implementations that depend on your hosting environment’s capabilities.

Ensure your hosting platform and CMS can enforce the access controls your copyright obligations require — and that those controls are consistently applied and regularly audited.

8. Security and Patron Privacy

Library security isn’t just about protecting your infrastructure — it’s about protecting your patrons’ right to explore ideas and information without surveillance. The technical and the ethical are inseparable here.

SSL/TLS: The Non-Negotiable Foundation

Every page of every library website must be served over HTTPS. This is true for your homepage, your catalog, your digital collections, and especially any page where a patron logs in, submits a form, or accesses their account. Unencrypted library web pages expose patron browsing behavior to network-level surveillance — which is antithetical to library values and, for public libraries, potentially a legal issue in states with strong library confidentiality statutes.

Most reputable hosts include free SSL via Let’s Encrypt. There is no reason for any library website to operate without it in 2025.

Hardening WordPress for Library Sites

WordPress is the most widely used CMS on the internet — which also makes it the most widely targeted by automated attacks. For library WordPress sites:

• Use unique, strong passwords for all accounts — administrator, editor, and author levels
• Enable two-factor authentication for all staff accounts
• Install a security plugin — Wordfence (free tier is robust) provides a firewall, malware scanning, and login protection
• Keep WordPress core, themes, and plugins updated — outdated plugins are the leading cause of WordPress compromises
• Remove plugins and themes that are no longer actively maintained or in use
• Limit login attempts to prevent brute-force attacks
• Use a Web Application Firewall (WAF) — many hosts include this at the server level

Protecting Patron Account Data

Libraries that offer patron login portals — for account management, holds, renewals, or access to digital resources — hold personal data that requires careful protection. Patron databases should be:

• Encrypted at rest — data stored on the server should be encrypted, not stored in plain text
• Backed up regularly with secure, restricted access to backup files
• Audited for access — who can query patron data and under what circumstances should be documented and reviewed
• Protected by session management — automatic logout after inactivity, especially important for shared public computers in library branches

Incident Response Planning

Every library with a web presence should have a documented plan for what happens when something goes wrong — a defacement, a data breach, a ransomware infection, or a prolonged outage. The plan doesn’t need to be lengthy, but it should answer: Who gets notified? Who has authority to take the site offline? Where is the most recent clean backup? Who is the hosting provider’s emergency contact? Assign these responsibilities before you need them.

9. Bandwidth, Storage, and Media Collections

For digital archives in particular, storage and bandwidth are not minor line items — they are the dominant infrastructure considerations. High-resolution scans of historical documents, archival audio recordings, digitized film, and photographic collections can collectively reach terabytes of data that must be stored reliably, delivered efficiently, and preserved for the long term.

Understanding Your Storage Requirements

The scale of your storage needs depends on your collection type. Some general reference points for planning:

• A high-quality archival TIFF scan of a single document page runs approximately 30–80MB
• A digitized 35mm photograph at archival quality is typically 50–100MB
• One hour of uncompressed archival audio (WAV) is approximately 600MB
• One hour of standard-definition video at archival quality is 10–50GB
• One hour of high-definition video at archival quality can exceed 100GB

A collection of 10,000 digitized photographs at archival quality can easily require 500GB to 1TB of storage. Planning for growth — both of existing collections and future digitization projects — is essential. Storage that seems ample today may be inadequate in three years.

Tiered Storage Strategies

Not all digital content needs to be served at the same speed or stored at the same cost. A tiered storage approach is standard practice in large digital archives:

• Hot storage (SSD/fast disk) — for frequently accessed content, derivative files for web delivery, and actively used databases; highest cost, fastest access
• Warm storage (standard disk or cloud object storage) — for less-frequently accessed content that still needs to be available on demand; moderate cost and access speed; Amazon S3 Standard or similar
• Cold/archival storage — for preservation masters and rarely accessed content; lowest cost, slowest retrieval; Amazon S3 Glacier, Backblaze B2, or tape-based storage

Web-deliverable derivatives (compressed JPEGs from TIFF masters, MP3s from WAV masters, lower-resolution video proxies) should be what your hosting server delivers to patrons — not the archival masters, which should remain in cold or warm storage.

Bandwidth for High-Traffic Collections

Digital collections that attract significant research traffic — a newspaper archive that becomes the subject of a news story, a digitized photograph collection featured in a publication, a historical document collection referenced in popular culture — can experience sudden, dramatic traffic spikes. Ensure your hosting plan has either unmetered bandwidth or sufficiently high limits that a traffic spike doesn’t result in overage charges or service throttling. CDN integration distributes the load and reduces the bandwidth consumed directly from your primary server.

10. Budgeting and Funding Strategies

Library budgets are perennially constrained, and digital infrastructure often competes with staffing, collections, and programming for limited resources. Here’s a realistic picture of what library web hosting actually costs — and where to find funding.

Funding Sources for Library Digital Infrastructure

Libraries have access to funding streams that can offset or fully cover web hosting and digital infrastructure costs:

• IMLS (Institute of Museum and Library Services) grants — IMLS funds digital infrastructure projects through its Grants to States program and competitive grant programs like the National Leadership Grants for Libraries
• State library agency grants — most state library agencies distribute IMLS Grants to States funding through competitive or formula-based grants that can include digital infrastructure
• NEH (National Endowment for the Humanities) — the Preservation and Access division funds digitization and digital preservation infrastructure for archives and special collections
• LSTA (Library Services and Technology Act) — federal funding distributed through state agencies, often available for technology infrastructure including hosting and digital collections
• Friends of the Library groups — for smaller libraries, Friends groups can be a practical source of funding for modest hosting costs that fall outside the main budget cycle

11. Mistakes Libraries Commonly Make

These are the patterns that come up repeatedly when libraries encounter digital infrastructure problems. They’re all preventable with the right planning.

Conflating Backup with Preservation

As discussed earlier, backup and preservation are different things with different purposes. Libraries that rely on nightly hosting backups as their only preservation strategy for digital collections are taking on significant risk. Backups protect against yesterday’s disaster. Preservation protects against the next twenty years of technological change. Both are necessary; neither substitutes for the other.

Letting URLs Break During Migrations

Every time a library migrates to a new CMS, redesigns its website, or moves to a new hosting provider, there’s a risk of breaking URLs that researchers and other institutions have cited, linked to, or bookmarked. A robust redirect strategy — mapping every old URL to its new equivalent — should be a non-negotiable deliverable of any migration project. Losing URL stability is a preservation failure that can’t be undone after the fact.

Serving Archival Masters Instead of Derivatives

A digital archive that serves 80MB TIFF files directly to web users is wasting bandwidth, slowing page loads, and creating an unnecessarily large attack surface for its archival masters. Create web-optimized derivatives for public delivery and keep masters in secured, separate storage.

Ignoring Accessibility Until It Becomes a Complaint

Accessibility retrofits are significantly more expensive than building accessibly from the start. And a formal ADA complaint or DOJ investigation is dramatically more expensive than either. Libraries with a genuine commitment to equitable access need to make accessibility a selection criterion for every hosting, CMS, and theme decision — not an afterthought.

No Documented Ownership of Web Accounts

When the person who set up the library’s hosting account, domain registration, or CMS admin leaves — voluntarily or otherwise — does your institution know all of the credentials they held? Libraries should maintain a secure, documented record of all web-related account credentials, updated whenever staff changes occur. Losing access to a domain or hosting account because the sole credential-holder is no longer available is a preventable crisis.

Under-Investing in Storage for Long-Term Collections

The cost of cloud storage has dropped dramatically — Backblaze B2 charges approximately $6 per terabyte per month. There is no longer a strong cost argument for under-investing in digital preservation storage. A library that loses irreplaceable digitized materials because storage felt too expensive to fully provision has made a false economy that cannot be corrected.

12. Building Your Launch or Migration Plan

Whether you’re establishing a new digital presence, migrating from an outdated hosting environment, or planning a major system upgrade, the following checklist provides a systematic framework for getting it right.

Infrastructure and Hosting Selection

• Document your institution’s specific hosting requirements — collection size, traffic patterns, ILS needs, accessibility obligations
• Determine whether VPS, cloud, managed WordPress, or consortial hosting best fits your needs and budget
• Confirm uptime guarantee is 99.9% or higher with a documented SLA
• Verify SSL is included and can be configured across all subdomains
• Confirm automated daily backups are included and stored off-server
• Evaluate data residency — where are servers physically located?
• Confirm the provider has experience with or support for your ILS/CMS of choice
• Review the renewal rate — not just the introductory price

Account Setup and Security

• Register domain in the institution’s administrative account — document credentials securely
• Enable two-factor authentication on hosting account, domain registrar, and CMS admin
• Activate SSL and force HTTPS across all pages including catalog and patron login
• Install and configure a security plugin (Wordfence for WordPress)
• Set up uptime monitoring — UptimeRobot free tier is sufficient for most libraries
• Configure privacy-respecting analytics — consider Matomo over Google Analytics
• Document all credentials and assign successor access to at least two staff members

Digital Collections and Preservation

• Implement 3-2-1 backup strategy for all digital collections
• Establish fixity checking schedule for preservation masters
• Set up persistent identifier system (ARK, Handle, or DOI) for collection items
• Create web-optimized derivatives for all archival masters — serve derivatives, not masters
• Configure OAI-PMH endpoint if participating in metadata harvesting networks
• Document and test URL redirect strategy before any migration goes live
• Verify IIIF server configuration if serving image collections (if applicable)

Compliance and Accessibility

• Run accessibility audit using WAVE or axe tools — address WCAG 2.1 AA failures
• Confirm patron login and account pages enforce session timeouts
• Review analytics and third-party tools for patron privacy implications
• Post a clear, accurate privacy policy reflecting your data practices
• Review copyright status and access controls for all digitized collections
• Confirm ADA/Section 508 compliance obligations and document compliance status

Before Going Live

• Test all pages on desktop, tablet, and mobile — including catalog and digital collection interfaces
• Verify all links — broken links in finding aids and collection pages damage researcher trust
• Test catalog search performance under realistic load conditions
• Confirm that archival masters are not publicly accessible via direct URL
• Run Google PageSpeed Insights on key public pages and address major issues
• Have at least two staff members conduct a full walkthrough before launch
• Notify DPLA, consortium partners, and search engines of any URL changes

---