Version 1.1 of the definition has been released. Please help updating it, contribute translations, and help us with the design of logos and buttons to identify free cultural works and licenses!


From Definition of Free Cultural Works
Revision as of 00:34, 25 August 2011 by (talk) (Added a link to an explanation video)
Jump to navigation Jump to search

Frequently Asked Questions about Open Source Hardware

What is open source hardware?

Our statement of principles puts it like this: "Open source hardware is hardware whose design is made publicly available so that anyone can study, modify, distribute, make, and sell the design or hardware based on that design. The hardware's source, the design from which it is made, is available in the preferred format for making modifications to it."

Open source hardware is also a growing community of companies, individuals, and groups designing and making lots of cool stuff! Some well-known examples include Arduino (an microcontroller development platform), Chumby (a wifi device), MakerBot (a 3D printer) but see this question for more. Open source hardware developers gather at events like the Open Hardware Summit and on online forums like the mailing list. They've ...

We think open source hardware is a great way to share knowledge and facilitate development of new products. We hope this FAQ helps you understand what it's all about and whether it makes sense for you.

Why make hardware open source?

What files should I share?

You should share all the files needed to build *and* modify your hardware.

For mechanical stuff, this means CAD drawings, IGES files, or STL files. For electronic projects, this means the schematics and circuit board layouts. With circuit boards, it's better to share the original files rather than Gerber files. (Gerber files are an intermediate format needed for manufacturing, but they're difficult to modify.)

What are other best practices for open source hardware?

1. Make it clear how your hardware is licensed by providing a copy of, or at least a web link to, the license with the hardware.

2. Put the OSHW logo on your hardware. You can find lots of different versions at

3. Keep your source files in a (free) publicly-available source code repository like Github. This makes it easier for people to track their changes to your files. It also makes it easier for them to send improvements back to you. The tools for this kind of data exchange are still pretty weak for hardware projects, but for software, they're mature.

Won't people rip me off?

People will rip you off in the sense that they will use your designs as the basis for more advanced designs. If you don't want that to happen, you should probably not call your hardware "open source."

Those of us who do build open source hardware want people to build on our designs, or at least think the benefits of the situation are worth the competition.

Why aren't non-commercial restrictions compatible with open source hardware?

There are a few reasons.

If you place a non-commercial restriction on your hardware design, other people don't have the same freedom to use the design in the ways that you can. That means, for example, that if you and someone else both release designs with non-commercial licenses, neither of you can make and sell hardware that builds on both of your designs. Rather than contributing to a commons of hardware designs for everyone to build on, you're limiting others to a very narrow range of possible uses for your design.

In particular, because making hardware invariably involves money, it's very difficult to make use of a hardware design without involving some commercial activity. For example, say a group of friends wanted to get together and order ten copies of a hardware design - something that's often much cheaper than each person ordering their own copy. If one person places the order and the others pay him back for their share, they'd probably be violating a non-commercial restriction. Or say someone wants to charge people to take a workshop in which they make and keep a copy of your hardware design - that's also commercial activity. In general, there are just very few ways for someone to use a hardware design without involving some sort of commercial activity.

Who makes open source hardware?

How to ensure that all modifications to my projects are put back into open source?


Dave Jones from the EEVblog explains some benefits of OSHW and how it works in this Youtube video