Learn how AlterSend and LocalSend differ in their key features, development activity, technology stack and community adoption, so you can decide which of these cloud file sync & share tools is best for you.
Last 30 days
Last commit
1 day agoRepository age
6 monthsVersion
v2.0.0License
Apache-2.0Repository
altersend
Last 30 days
Last commit
5 days agoRepository age
4 yearsVersion
v1.18.2License
Apache-2.0Repository
localsend/localsend
Both AlterSend and LocalSend have their unique strengths and serve similar purposes effectively. Consider your specific needs regarding popularity, growth, activity, maturity, licensing and features when making your decision.
LocalSend significantly outpaces AlterSend in community adoption with 99,137 stars compared to 2,249 stars on GitHub. This 44.1x difference suggests LocalSend has a much larger and more active community. In terms of developer contributions, LocalSend has 5,680 forks, indicating strong developer engagement.
AlterSend is growing faster, adding 383 stars in the last 30 days (+21%) against adding 4,553 stars for LocalSend (+4.8%). AlterSend is the smaller project of the two, so it is closing the gap rather than extending a lead.
Both projects show recent activity, with AlterSend last updated 1 day ago and LocalSend 5 days ago.
LocalSend has been in development longer, starting 4 years ago, compared to AlterSend which began 6 months ago. This 3.5-year head start suggests LocalSend may have more mature features and established processes.
Both projects use the Apache-2.0 license, providing identical terms for usage and distribution.
Both tools serve similar use cases in Cloud File Sync & Share.