For a hobbyist developing a device, certification is not pleasant.

I am wondering if implementing USB in any way is patented or needs a certification?

I am concerned about both protocol (USB-2,3) and headers (USB-A, B, C).

I am also curious if the processor producers should pay to use USB output for their chips?


1 Answer 1


You do not need to pay anything if USB logo and the word "USB" is not important to you and you are happy using a non-unique Vendor ID code.

The logo is protected by trademark and copyright and you receive a license to use it with conditions. One of those conditions is that you conduct certification testing. The Vendor ID is how they make sure you pay to support the spec.

There are certainly patents associated with USB, however, this will only become an issue if you attempt to reimplement (fork) USB itself, simply designing a device, but not testing it or paying for the logo, will not likely run into patent issues.

There is nothing wrong with using a "USB" connector for other purposes, e.g. USB as a device charging port started out as this kind of "off-label" use, or USB reusing interface for a different signal scheme of your design (custom UART). As long as you do not try to make this into its own spec or patent that starts to look like USB... which is when you would need to understand the patents.

Most companies selling USB products pay to join the USB organization to obtain a vendor ID and may conduct some conformance testing depending on what they make.

  1. USB Implementers forum (USB-IF) owns the USB Specification, logo, and associated trademarks (https://www.usb.org)
  • Specifications, for the most part, are free to read
  • USB-IF maintains the list of vendor IDs
  • USB-IF sets the rules for testing and licenses the third party labs to do testing
  1. Every organization that wishes to obtain a Vendor ID joins USB-IF and pays a $5000 annual membership fee or a one time $6000 fee for ID without membership. (https://www.usb.org/getting-vendor-id)
  • Some microcontroller companies let you sublicense use their Vendor ID for prototypes and testing.
  • There is an "unnoficial" vendor ID 0xF055 used by open source projects.
  • Joining also gives you the right to influence the future of the specifications.
  • All assigned Vendor IDs are listed here, every one of those companies has paid to obtain this number. Note that many of companies that make processors and microcontrollers are on there.
  1. In order to use the logo and call yourself a USB device you must pay a license fee of $3500 for the logo. (https://www.usb.org/logo-license)
  • As a condition of the license, you must pass a compliance test. (https://www.usb.org/compliance)
  • In order to pass a compliance test you must pay an outside lab and provide test samples that may cost you money.
  • Some devices may not require testing, usually applicable if you make many similar devices and do not want to test all of them.
  • If you are a member paying annual dues, the $3500 fee is waived.

As an aside, conformance testing in and of itself is a great engineering challenge, while you may wish to avoid the fees associated with USB and conformance testing with independent lab and this is reasonable for a hobbyist it is still a good exercise to go through the certification tests on your own.

It serves as a design checklist and implementation guide, and is also there to ensure that your device is inter-operable with other USB devices. The last thing you would want as a designer, even of a hobby product, is a USB widget that damages or is not interoperable with other USB devices.

  • \$\begingroup\$ Thank you very much for great information you provided. There is a confusion. What does a device here mean? Is it the USB component or is it the circuit board or the package or the system of devices making one unit? \$\endgroup\$
    – ar2015
    Jul 28, 2019 at 14:01
  • 7
    \$\begingroup\$ While most of this is about the same advice I'd give, I do have to contest your point that there is nothing wrong with using USB connectors for other purposes. Perhaps there is not anything legally wrong with it but it bears the risk of causing confusion to customers or harm to their devices, especially if you put voltages other than 5V on the power lines, or try to supply power on the data lines. \$\endgroup\$
    – Hearth
    Jul 28, 2019 at 16:29
  • 1
    \$\begingroup\$ @Hearth this is certainly a valid concern, however I would point to thunderbolt from Apple, which is USB-C connector, but completely different signaling spec as being something already in the wild. Another use case is non-standard connectors for USB within controlled conditions, for cabinet or small enclosure applications, drones, etc. For purely experimental/hobby purposes it is a high tech connector to develop your custom signaling scheme, eventually maybe you design a custom connector. \$\endgroup\$
    – crasic
    Jul 29, 2019 at 2:46
  • 1
    \$\begingroup\$ It seems that you can get a license to the patents required to make a compliant device for free by executing the Adopters' agreement. There do not seem to be any fees involved.usb.org/document-library/usb-30-adopters-agreement. \$\endgroup\$ Aug 2, 2019 at 20:42
  • 1
    \$\begingroup\$ @GeorgeWhite in essence that agreement allows you to use the specifications (which are freely available, but this formalizes that relationship) and associated patents royalty free. It does not grant you "compliance" which is a formal thing that requires membership and other additional one-time fees for testing and such. This agreement also codifies my hand waving point of "do what you will but do not fork USB spec" \$\endgroup\$
    – crasic
    Sep 8, 2019 at 1:21

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.