openboard.ch

OpenBoard is available as a free download for Windows, macOS, and Linux, and you can start using it immediately after installing — no registration or account is required. This guide covers what you need before downloading, how to get the installer, and how to verify your setup works, based on information published on openboard.ch.

What you need before downloading

OpenBoard runs on all three major desktop platforms, so the main prerequisite is simply a supported operating system:

• Windows
• macOS
• Linux

You do not need an interactive whiteboard to use the software. According to the official site, OpenBoard can be used:

• With an interactive whiteboard,
• In a dual-screen setup with a pen-tablet display and a beamer,
• Or on your computer alone, without any additional hardware.

That last point matters if you are evaluating the software before your classroom hardware arrives — you can install and test it on a normal laptop first.

Step 1: Download OpenBoard from the official site

1. Go to openboard.ch.
2. Use the Download link in the site navigation.
3. Choose the installer for your operating system (Windows, macOS, or Linux).

The site states the software is free and that no registration is required, so you should not be asked to create an account or provide payment details to obtain it.

Step 2: Install and launch

The official site describes installation as easy: "Simply download and start using it right away." In practice, that means running the installer for your platform and then opening the application from your applications menu or desktop.

If you want to confirm the software is genuinely open source before installing, note that OpenBoard is released under the GPLv3 License and maintained by the community on GitHub. You can inspect the source there if that matters for your institution's software approval process.

Step 3: Verify it works

Once OpenBoard is open, a quick check confirms your setup is functional:

• Try writing or annotating with whatever input you have — a pen tablet, an interactive whiteboard, or even a mouse. The site explicitly lists mouse input as an option, so a failed pen connection does not mean the install failed.
• If you are using a dual-screen configuration, confirm the pen-tablet display and beamer are both detected by your operating system before troubleshooting inside OpenBoard.

Where to get help

The site navigation includes a Documentation section alongside Download, GitHub, and Help. If something does not work after installation, those are the official starting points rather than third-party tutorials.

Common questions

Is OpenBoard really free? Yes. The official site describes it as free and open source, released under GPLv3.

Do I need to register? No. The site states no registration is required.

Which platforms are supported? Windows, macOS, and Linux.

Who maintains it? OpenBoard is maintained by the Education Department (DIP) of the canton of Geneva, Switzerland, with contributions from the University of Lausanne. It was originally forked from Open-Sankoré 2.0, which was itself based on Uniboard, with the fork intended to refocus on core classroom teaching functionality and ease of use.

Can I use it without an interactive whiteboard? Yes — it also runs on a plain computer with no additional hardware.

An open-source UI element library is a collection of individual, ready-made interface pieces—buttons, cards, inputs, toggles, loaders—that you copy into your own project and adapt. A UI framework, by contrast, is a structured system of components, conventions, and often a theming layer that governs how your whole interface is built. The practical difference: an element library gives you a snippet; a framework gives you a way of working. If you need a polished button in ten minutes, reach for the element library. If you're building a 40-screen product with a team, you probably want the framework.

What "open-source UI element library" actually means

The term gets used loosely, so it helps to separate the parts:

• Open-source: the code is publicly available, and the license tells you what you may do with it—copy, modify, redistribute, or use commercially.
• UI element: a single, self-contained piece of interface, usually small enough to read in one sitting. A button with hover states, a pricing card, a search field.
• Library: a browsable, searchable collection of those elements, typically contributed by many different people.

On a site like Uiverse, elements are shared by a community and written in plain CSS or Tailwind. You find one you like, copy the markup and styles, paste them into your project, and adjust colors, spacing, and text to fit. There's no package to install and no build step required—which is exactly the appeal, and also the source of most of the confusion.

Element library vs. UI framework: the core differences

The table isn't a verdict. It's a map of trade-offs. Element libraries win on speed and freedom; frameworks win on consistency and maintenance.

Licensing and attribution: what to check before you paste

This is where people get into trouble, and it's worth slowing down for.

1. Find the license. Every element or collection should state one. Common open-source licenses include MIT, Apache-2.0, and BSD. Some projects use copyleft licenses like GPL, which can impose obligations if you redistribute your code.
2. Understand what the license permits. MIT and Apache-2.0 are permissive: you can typically use the code in commercial and closed-source projects. Copyleft licenses may require you to release derivative source under the same terms.
3. Check attribution requirements. Permissive licenses usually require you to keep the copyright notice and license text somewhere in your project. That's a real obligation, not a formality.
4. Look for per-element terms. On community sites, the site's overall terms and the individual contributor's stated wishes may differ. If a contributor asks for credit, honor it.
5. When in doubt, ask or avoid. If a snippet has no license at all, you don't have clear permission to reuse it. Treat "no license" as "not open source," even if the code is publicly visible.

This article is general information, not legal advice. For commercial products with real exposure, have someone qualified review the licenses you're relying on.

How to use a community element in your project: a practical workflow

Here's a repeatable process that avoids most of the usual mess.

1. Start from a real need, not a browsing session

Decide what you need first—"a compact primary button with a loading state"—then search. Browsing aimlessly produces a pile of pretty snippets that don't fit together.

2. Copy the smallest version that works

Take the markup and the styles. Strip anything you don't need: demo wrappers, extra animations, decorative layers. Less code means fewer surprises.

3. Convert it to your conventions

If your project uses design tokens or CSS variables, replace hard-coded values:

/* Before: hard-coded */
.button { background: #4f46e5; border-radius: 8px; }

/* After: token-based */
.button { background: var(--color-primary); border-radius: var(--radius-md); }

This one step is what keeps a copied element from looking like a foreign object in your UI.

4. Check accessibility before you ship

Community elements vary widely here. Verify at minimum:

• Keyboard focus is visible and the element is reachable by Tab.
• Color contrast meets WCAG AA (4.5:1 for normal text).
• Interactive elements use semantic HTML (<button>, not a clickable <div>).
• Form inputs have associated labels.
• Motion respects prefers-reduced-motion.

5. Test in context

Paste it into a real page with real content. Long labels, small screens, and dark mode break more copied elements than anything else.

6. Note where it came from

Keep a short comment or an internal credits file: source, license, date. Future you—and your legal reviewer—will be grateful.

Where element libraries genuinely shine

• Prototypes and demos: you need something clickable today, not a design system.
• Landing pages and marketing sites: a handful of distinctive elements, each custom.
• Filling gaps: your framework lacks one specific component, and you don't want to build it from scratch.
• Learning: reading well-made CSS is one of the fastest ways to improve.
• Small projects: a personal site doesn't need a theming architecture.

Where they fall short

• Consistency at scale: ten elements from ten contributors rarely look like one product.
• Maintenance: you own every copy. When your design changes, you edit each one.
• Accessibility debt: you inherit whatever the contributor did or didn't do.
• No upstream fixes: a bug fixed in the original won't reach your copy.
• Integration friction: different naming conventions, different units, different assumptions about resets.

When to choose which

Choose an element library when the scope is small, the timeline is short, or you need a few distinctive pieces rather than a whole system.

Choose a framework or design system when multiple people build multiple screens over months, when consistency is a product requirement, or when accessibility and theming need to be guaranteed rather than checked.

A hybrid works well for many teams: adopt a framework for the structural components—forms, navigation, layout—and borrow individual elements for the places where you want personality. Just route every borrowed element through the same token and accessibility checks, so it lands as part of your system rather than beside it.

The short version: open-source UI element libraries are a fast, flexible way to get good-looking interface pieces into a project. They are not a substitute for a design system, and the license and accessibility details are the part worth reading carefully.

OpenBoard is a fork of Open-Sankoré 2.0, which was itself based on Uniboard. The fork was created to refocus the software on its original core purpose: a teacher’s work in the classroom, with ease of use as the priority. Future development is meant to follow those same principles. The project is currently maintained by the Education Department (DIP) of the canton of Geneva, Switzerland, with support from the University of Lausanne.

The lineage: Uniboard → Open-Sankoré → OpenBoard

The family tree matters because it explains why OpenBoard looks and behaves the way it does.

• Uniboard was developed in 2003 by the University of Lausanne.
• Open-Sankoré 2.0 came later, built on Uniboard.
• OpenBoard was forked from Open-Sankoré 2.0.

Each step kept the interactive whiteboard foundation, but OpenBoard’s fork was a deliberate narrowing of scope. Rather than accumulating features, the project went back to what a teacher actually needs during a lesson.

Why the fork happened

The stated reason for creating OpenBoard was to refocus the software on its original core functionalities and values — specifically, the work of a teacher in a classroom — and to privilege ease of use. The site describes OpenBoard as “easy to use yet powerful,” a tool that “can help you do your job and does not get in the way.”

That principle is also the stated basis for how the software will evolve: “The evolution of this software will therefore take place in accordance with these core principles.”

If you are choosing between OpenBoard and a feature-heavy whiteboard suite, this is the key distinction. OpenBoard is not trying to be everything; it is trying to stay out of the way of teaching.

Who is involved

OpenBoard is not a solo hobby project. According to the site:

• It is currently maintained by the Education Department (DIP) of the canton of Geneva, Switzerland.
• The University of Lausanne, which developed the original Uniboard software in 2003, has joined the effort through a logistical and financial contribution.
• An association project was to be developed in 2019.
• In June 2016, representatives from the universities of Lausanne, Neuchâtel, Fribourg and Geneva, the education departments of the cantons of Geneva and Jura, and various institutions from the canton of Vaud met to reflect together on the desired evolution of OpenBoard.

This institutional backing is worth noting if you are evaluating long-term viability for a school or university deployment. The project is tied to public education bodies in Switzerland, not just to individual volunteers.

What’s next

The site states that interest is growing fast across Switzerland, but also in Europe and North America. It also mentions that a Swiss association project was planned for 2019 as part of the effort to structure the project’s future.

Beyond that, the direction is already defined by the fork’s founding principle: continued evolution in line with the core values of classroom teaching and ease of use. The project is community-maintained on GitHub and released under the GPLv3 License, so its roadmap is public and open to contribution.

What this means if you’re deciding whether to adopt it

• If you want a whiteboard tool that stays simple and teaching-focused, the origin story is a point in its favor — the fork exists specifically to protect that focus.
• If you need institutional longevity, the involvement of the canton of Geneva’s education department and the University of Lausanne is relevant evidence.
• If you want to follow or influence development, the GitHub repository is the place where the community maintains it.

OpenBoard runs on Windows, macOS and Linux, and can be used with an interactive whiteboard, in a dual-screen setup with a pen-tablet display and a beamer, or on a computer without additional hardware.

OpenBoard runs on Windows, macOS, and Linux, and it works with an interactive whiteboard, a dual-screen setup (pen-tablet display plus a beamer), or a plain computer with no extra hardware. You can write and annotate with a pen tablet, an interactive whiteboard, or even a mouse. It is free, open source under GPLv3, and requires no registration to download and start using.

Supported operating systems

OpenBoard is cross-platform. The official site lists three supported platforms:

• Windows
• macOS
• Linux

Because the same application is available on all three, you can stay with the operating system you already prefer rather than switching to match the software.

Supported hardware setups

OpenBoard is designed primarily for schools and universities, and it adapts to several classroom configurations. The site describes three ways to use it:

The dual-screen arrangement pairs a touchscreen or pen-tablet display with a second display such as a projector, so you can write on one surface while the class sees the output on another.

How you write and annotate

Input is not limited to a single device. According to the site, you can write and annotate your course using:

• a pen tablet
• an interactive whiteboard
• a mouse

The project notes that the writing experience is under continuous improvement, so handwriting quality and responsiveness are active areas of development rather than fixed features.

What you need to get started

The requirements are deliberately minimal:

1. Download OpenBoard for Windows, macOS, or Linux.
2. Install and launch it — the site describes installation as easy, with no registration required.
3. Start using it right away, with or without additional hardware.

There is no account creation step and no registration gate described on the site.

Where OpenBoard comes from

OpenBoard was forked from Open-Sankoré 2.0, which was itself based on Uniboard. The fork was created to refocus the software on its original core purpose — a teacher's work in the classroom — with an emphasis on ease of use. It is currently maintained by the Education Department (DIP) of the canton of Geneva, Switzerland, with logistical and financial contributions from the University of Lausanne, which developed the original Uniboard software in 2003.

Choosing the right setup for your situation

• If you already have an interactive whiteboard, use OpenBoard with it directly.
• If you have a touchscreen or pen-tablet display plus a projector, the dual-screen setup lets you write on the tablet while projecting to the class.
• If you have neither, you can still run OpenBoard on an ordinary computer and annotate with a mouse — useful for preparation, remote teaching, or smaller sessions.

In all three cases the software is the same; only the input and display hardware change.

Yes. OpenBoard is free to download and is released as open-source software under the GPLv3 License. The project is maintained by the community on GitHub, with institutional backing from the Education Department (DIP) of the canton of Geneva, Switzerland, and a logistical and financial contribution from the University of Lausanne.

What "free and open source" means here

Two separate things are true at once, and it helps to keep them apart:

• No cost to get started. The site states you can "Get OpenBoard for free" for Windows, macOS and Linux, with easy installation and no registration required. You download it and start using it.
• Open source under GPLv3. The source code is published and licensed under GPLv3, and the project is maintained by the community on GitHub. That means the code can be inspected, and the license governs how it can be reused and redistributed.

The site does not mention paid tiers, subscriptions, or payment platforms, so there is no indication of a commercial edition being sold on the site itself.

Who stands behind it

OpenBoard is not an anonymous hobby project. According to the site:

• It is currently maintained by the Education Department (DIP) of the canton of Geneva, Switzerland.
• The University of Lausanne, which developed the original Uniboard software in 2003, contributes logistically and financially.
• An association project was planned for 2019, and a June 2016 meeting brought together representatives from the universities of Lausanne, Neuchâtel, Fribourg and Geneva, the education departments of the cantons of Geneva and Jura, and institutions from the canton of Vaud.

This matters if you are choosing software for an institution: the project has a public-sector and academic lineage rather than a single vendor.

Where it came from

OpenBoard was forked from Open-Sankoré 2.0, which was itself based on Uniboard. The stated reason for the fork was to refocus the software on its original core purpose — a teacher's work in a classroom — and to prioritise ease of use. Future development is meant to follow those same principles.

Practical implications for your decision

If your requirement is a no-cost, cross-platform whiteboard application that you can install without creating an account, OpenBoard meets it on the evidence above. If your requirement is a specific support contract or a vendor SLA, the site does not describe one — the maintenance model described is community and institutional rather than commercial.