Koha can absolutely run a school library. For many schools it is also more system than they need to look after.
What decides it is not the size of your collection. It is who will look after the software. If you have a school IT team with time, Koha is an excellent free choice. If the honest answer is "me, and I am also teaching", read on before committing.
What a school library actually needs
- A catalog of what you own
- Issuing and returning books to students
- Student records, ideally without typing them all in
- Overdue reminders that reach someone
- A catalog students can search themselves
- Simple reports — what is out, what is missing, what is popular
And a list of things school libraries almost never need: acquisitions budgets and fund accounting, serials prediction, interlibrary loan, electronic resource licensing.
What Koha gives a school
Everything on the first list, done well and free of charge. Cataloging, circulation, student records, overdue notices, a public catalog and reports are all standard.
It also gives you everything on the second list, which you will never open. That is not a problem — unused modules sit quietly. It is worth knowing so the interface does not feel intimidating: most school libraries use perhaps a fifth of Koha, and that fifth works well.
What Koha asks in return
The deciding section. Running Koha means somebody is responsible for:
- A server — bought or rented, kept running and updated. Not a school PC under a desk.
- Upgrades — twice a year, ideally tested first.
- Backups — automated, kept somewhere else, and restored once to prove they work.
- Someone who understands MARC — the cataloging format, which is genuinely unlike anything else.
- Email that actually delivers. This one catches every school. Putting an email address into Koha is not enough: without the right DNS settings your overdue notices land in parents' spam folders and nobody ever sees them.
- Someone to write the notice templates — the wording of every overdue and reminder message.
None of this is difficult for a technical person. All of it is a real, recurring commitment. See our installation guide and hosting guide for what is involved.
Do you need MARC records?
Schools often do not know what MARC is, and reasonably ask whether they must type long catalog records for every book.
No. Koha can search other libraries' catalogues and copy their records for you. You type or scan the ISBN, Koha finds the full record elsewhere, you accept it, and the book is cataloged in seconds — that is copy cataloging, and it is how nearly all school cataloging should be done.
You need this set up before you start, or you will type records by hand and conclude Koha is slow. Our MARC guide covers what the records contain.
Koha versus school-specific systems
| Koha | School library products | A spreadsheet | |
|---|---|---|---|
| Software cost | Free | Annual fee | Free |
| Running cost | Hosting + maintenance | Included | None |
| Features | Far more than needed | Sized for schools | Minimal |
| Student catalog | Yes | Yes | No |
| Overdue notices | Yes, once configured | Yes | No |
| Who maintains it | You | The vendor | You |
| Your data if you leave | Yours, open format | Depends on contract | Yours |
School-specific products are simpler and someone else maintains them; you pay annually and are more tied to that supplier. Koha costs nothing to license and asks for maintenance instead. Both are reasonable — see our fuller comparison.
If you are currently on a spreadsheet, almost anything is an improvement. A spreadsheet cannot tell a student what is on the shelf, and it cannot tell you who has your missing book.
What it costs a school
For a typical school library — around 8,000 titles, one or two staff, one site — expect roughly USD 1,200–3,400 in the first year for a paid setup including hosting, configuration, getting your existing records in, and training. After that, hosting and support recur.
Self-installing removes the setup cost and replaces it with your own time. Indicative figures; see our cost breakdown and hosting costs.
Student privacy
A section most library software articles skip, and schools should not.
Your system will record which student borrowed which book. Decide deliberately:
- How long to keep reading history. Koha can forget what a student borrowed once it is returned. For a school, keeping less is usually the right answer.
- Who can see it. Restrict staff permissions so not everyone can browse a child's borrowing record.
- Parental access. Decide your policy before a parent asks, not during the conversation.
- What leaves with the student. Have a rule for records when a pupil moves on.
Data protection rules differ by country and by school authority — check what applies to you rather than assuming. The point is to make these choices on purpose.
Getting started without a technical team
Three realistic routes:
- A hosted Koha service. Someone installs and maintains real Koha for you; you pay for the service.
- A complete setup, hosted and managed. Nothing to install and no server to buy — the system is ready, the overdue emails already work, backups run daily.
- A parent institution's existing system. If your school is part of a group already running Koha, joining it is often cheapest.
For a school with no IT staff, the second is usually right, and it is worth being plain about why: nothing to install, no server to buy, nobody to call at 2am, overdue emails that actually reach parents because the mail side is already configured, a daily backup that lands in the school's own Google Drive, and books checked in and out by scanning with a phone camera — so there is no scanner to buy for the desk. Students sign in with their existing Google account, so there are no passwords to issue or reset.
That is what a system set up and hosted for you means in practice. One yearly figure covers setup, hosting, backups and upgrades, instead of buying a server and finding someone to look after it.
Is Koha right for your school?
A plain checklist:
- Do you have IT staff with time allocated to this? → Koha, self-hosted, is a good choice.
- Is your school part of a group already running Koha? → join it.
- Do you want a proper catalog but have nobody to run a server? → have it hosted; do not self-install.
- Do you need it working next week with no budget and no help? → a school-specific product may genuinely suit you better.
We would rather tell you that last one honestly than sell you something you cannot maintain.
Running a school library? Tell us roughly how many books you have and what you use now. We will tell you straight whether Koha fits — and what it would take to get you running.