October 4, 2022
Netflix begins Password-Sharing Crackdown

Sorry Netflix Moochers, the Streaming Service Wants to End Password Sharing

Netflix is experimenting with its first series of security measures, designed to limit password sharing without proper authorization…

Netflix now claims approximately two million subscribers worldwide, making it the largest streaming service on the planet. Disney+ just hit a milestone by reaching 100 million paying customers, which represents half of Netflix’s figure. However, this is very impressive given Disney launched its streaming platform only about 17 months ago. Yet, Netflix remains the most popular. And now, the company is taking steps to ensure that its service is used legitimately.

Netflix Begins Password-Sharing Crackdown

Netflix has long known and tolerated nearly unfettered password sharing among its subscribers and non-paying consumers. But, that benevolence might be coming to an end in the near future. The streaming platform is deploying various measures in different markets in order to stop or limit password sharing.

Though the company will not provide details about how it is preventing passwords from being shared, it does say that it will ask for verification when it suspects someone other than an authorized viewer is attempting to use the service. Of course, this is very difficult because not necessarily everyone who isn’t paying for subscription is ​unauthorized to access the platform. For instance, husbands might share their login credentials with their wives, parents were their children, older siblings with younger brothers and sisters, and so on.

Still, it’s definitely a problem that the company needs to address given some estimates calculate the streaming service loses as much as $1.6 billion per year because of password sharing. That gives Netflix plenty of incentive to attempt to eliminate or greatly reduce the practice.

William Boleys

Will is an experienced freelance writer who covers a wide range of topics, including apps, social media, and search.

View all posts by William Boleys →