Like A WS2812 But With Dual Data Line For Added Protection

The WS2813 is not nearly as widely used as the WS2812B because of its higher price and limited innovation.

It’s fundamental advantage is an additional second data line that acts as a fallback should one controller in a string fail.

All the other WS2813 improvements like a higher refresh rate were silently back-ported to the WS2812, too.

When To Use

WS2813 can be used interchangeably with the WS2812.

Whenever the installation of WS2812 does not allow for later servicing, or when you need very high reliability, then investing in WS2813 and its second data line can be a good idea.

When To Not Use

For hobbyist projects or any other scenario where you can easily replace LED, you do not need a second fallback data wire.

Use the WS2812B instead.


WS2813 datasheet


Please do leave comments below. I am using utteran.ce, an open-source and ad-free light-weight commenting system.

Here is how your comments are stored

Whenever you leave a comment, a new github issue is created on your behalf.

  • All comments become trackable issues in the Github Issues section, and I (and you) can follow up on them.

  • There is no third-party provider, no disrupting ads, and everything remains transparent inside github.

Github Users Yes, Spammers No

To keep spammers out and comments attributable, all you do is log in using your (free) github account and grant the permission to submit issues on your behalf.

If you don’t have a github account yet, go get yourself one - it’s free and simple.

If for any reason you do not feel comfortable with letting the commenting system submit issues for you, then visit Github Issues directly, i.e. by clicking the red button Submit Issue at the bottom of each page, and submit your issue manually. You control everything.


For chit-chat and quick questions, feel free to visit and participate in Discussions. They work much like classic forums or bulletin boards. Just keep in mind: your valued input isn’t equally well trackable there.

  Show on Github    Submit Issue

(content created Mar 04, 2024 - last updated Mar 19, 2024)