LinkDroid for Linkwarden

A companion Android app for Linkwarden, honestly reviewed. If you’re already self-hosting your bookmarks, here’s whether this is worth installing.

TL;DR

• What it is: A native Android app that gives your self-hosted Linkwarden instance a mobile home — primarily through Android’s share menu and a built-in web view [README].
• Who it’s for: Existing Linkwarden users on Android who want to save links on the go without opening a browser tab every time [README][2].
• Cost: Free. Available exclusively on F-Droid, not Google Play [README].
• Key strength: The Android share intent works the way you’d expect — tap share on any page, pick LinkDroid, link goes to Linkwarden. One user in the Lemmy community confirmed it works with SSO setups, which matters if your Linkwarden instance is behind an auth layer [2].
• Key weakness: This is a thin client, not a full-featured app. You’re getting a share button and a wrapper around the Linkwarden web UI. If you were hoping for offline access or a native reading experience, that’s not what this is [README][3].
• Dependency: Requires a running Linkwarden instance. If you don’t already have Linkwarden self-hosted or on Linkwarden’s cloud plan, LinkDroid does nothing [README].

---

What is LinkDroid for Linkwarden

LinkDroid is a native Android application whose entire purpose is bridging the gap between Android’s share system and a self-hosted Linkwarden server. When you find an article you want to save in Chrome, Reddit, or anywhere else that has a share button, you tap share, select LinkDroid, and the URL goes straight to your Linkwarden instance — no browser tab, no login prompt, no copy-pasting [README].

Beyond the share intent, the app provides a drawer-based settings interface (where you enter your Linkwarden server URL and authentication token), a connection tester, and a built-in web view that loads Linkwarden’s web interface directly in the app rather than bouncing you to your phone’s browser [README].

The project started as a fork of Daniel Brendel’s HortusFox Android app and was adapted for Linkwarden by David Aderbauer, who has maintained it since 2024. It sits at 145 stars on the GitHub mirror, though the canonical repo is on GitLab [README]. The primary distribution channel is F-Droid [README][4].

The developer has been explicit about one thing worth knowing upfront: the app will not appear on Google Play-verified devices if Google mandates developer verification as planned. The README opens with a strongly-worded statement about this, citing the F-Droid project’s concerns about the policy. If you’re outside the F-Droid ecosystem or reliant on Google Play, this matters [README].

---

Why People Choose It

The use case is narrow but real. Linkwarden, the server it connects to, has earned consistent praise as a self-hosted read-it-later and bookmark management solution. One detailed XDA Developers review [3] called it “the undisputed champion” after testing multiple options post-Pocket, specifically praising its reader view customization, collections-and-tags organization, and smooth animations.

The problem every self-hosted bookmark manager faces is mobile. Opening a browser, navigating to your instance URL, finding the save button — it’s too many steps. Browser extensions handle desktop saving well, but Android needs a share target. That’s the problem LinkDroid solves.

From the Lemmy community thread on Linkwarden 2.12 [2], one user put it plainly: “Creates a nice share target on android so any share button gives the option of sending the link to linkwarden.” Another user who had been using LinkGuardian (a competing Android app) tried LinkDroid and switched: “You know what, I like it more than LinkGuardian. Great suggestion!” [2]. A third user noted it works with their SSO setup, which is a non-trivial requirement for anyone running Linkwarden behind an identity provider [2].

The XDA review [3] observed that Linkwarden’s “community-created mobile apps” maintain the same attention to detail as the main interface — though it didn’t go deep on LinkDroid specifically. The general takeaway is that mobile access is treated as a first-class concern in the Linkwarden ecosystem, and LinkDroid is currently the primary answer on Android.

The v2.0.0 release, flagged by selfh.st in December 2024 [4], marked a meaningful maturation: default tag support (so every link you save via the share menu automatically gets tagged), the option to open links in your system browser instead of the built-in web view, a restyled interface, a new app icon, a proper tablet layout, and expanded language support. Before this release, the app was fairly minimal; after it, it started resembling something you’d recommend to someone who isn’t technically inclined.

---

Features

Based on the README and v2.0.0 release notes:

Core functionality:

• Android share intent integration — share any URL to Linkwarden from any app [README]
• Built-in web view loading the Linkwarden web interface [README]
• Settings drawer for server URL and authentication token [README]
• Connection testing before you commit to a setup [README]

v2.0.0 additions [4]:

• Default tags support — auto-tag every saved link at share time
• Option to open links in the system browser instead of the built-in web view
• Tablet layout for larger Android screens
• Restyled interface with a new app icon
• Increased language support (translations via Weblate, with Italian, French, and Chinese listed as priorities) [README]

Design and platform:

• Material Design 3 components throughout [README]
• Dark mode support [README]
• Responsive design for phones and tablets [README]
• Built with Java and AndroidX libraries [README]

Privacy:

• No tracking or analytics [README]
• No third-party services required — direct connection to your Linkwarden instance only [README]
• The entire request path goes from your phone to your server, nowhere else [README]

What it doesn’t do:

• Offline access — you need a live connection to your Linkwarden instance
• Native reading mode — reading is handled by Linkwarden’s web UI inside the web view
• Bulk import or link management — this is a save-and-browse client, not a full management interface
• iOS support — Android only [README]

---

Pricing: SaaS vs Self-Hosted Math

LinkDroid itself costs nothing. It’s GPLv3-licensed (formerly MIT) and distributed free through F-Droid [README]. There’s no premium tier, no in-app purchase, no ads.

The cost question is really about Linkwarden, the server LinkDroid connects to.

Linkwarden self-hosted: Free. You run it on your own VPS. A basic Linkwarden instance runs comfortably on a $4–6/month VPS. Linkwarden uses Docker Compose for deployment [1]. The full software stack is open-source.

Linkwarden Cloud: The Linkwarden project offers a managed cloud plan for users who don’t want to maintain a server. Specific pricing wasn’t available in the sources reviewed, but the option exists for users who want Linkwarden’s features without the infrastructure work [2].

What you’re replacing: Pocket was free until Mozilla killed it. Raindrop.io’s free tier covers basics but limits offline access and advanced features. Pinboard costs $11/year. Instapaper is free with a premium tier. None of these give you the data sovereignty or the full content archiving that Linkwarden does.

The honest math: if you’re already self-hosting Linkwarden, LinkDroid adds zero marginal cost and meaningfully improves the mobile workflow. If you’re not self-hosting Linkwarden, you’re looking at a one-time setup cost (a few hours and a $5/month VPS) before LinkDroid becomes useful to you at all.

---

Deployment Reality Check

Installing LinkDroid is easy. You install it from F-Droid, open the settings drawer, paste your Linkwarden server URL and API token, hit test connection, and you’re done [README]. There’s no server-side configuration required — Linkwarden’s API was there already.

The harder part is having a Linkwarden instance to connect to. If you don’t already have one, the idroot.us guide [1] covers both Docker-based and manual installation on Linux. The short version: Docker Compose is the recommended path, you need a VPS with a public domain for HTTPS, and you need PostgreSQL plus an SMTP provider for email notifications. The guide rates it as accessible for Linux users with basic command-line experience [1].

Android version requirements: The current minimum is Android 5.0, but the README notes this is being bumped to Android 8.1 in the next release to enable new features [README]. If you’re on an older device, check before upgrading.

F-Droid only: This is the real friction point for some users. If you don’t have F-Droid installed, you’ll need to install it first, which requires allowing app installs from unknown sources. For users who exclusively use Google Play, this is an extra step. The developer has signaled clearly that this won’t change if Google’s developer verification mandate goes through [README].

SSO compatibility: At least one user has confirmed the app works correctly with SSO-protected Linkwarden instances [2]. Setup requires using an authentication token rather than username/password, which SSO deployments typically support via API tokens.

What can go sideways:

• If your Linkwarden instance runs on a self-signed certificate or non-standard port, the built-in web view may behave unexpectedly — this is an Android WebView limitation, not specific to LinkDroid.
• The app is maintained by a solo developer as a side project. The v2.0.0 release showed active development, but the pace will vary.

---

Pros and Cons

Pros

• Zero cost. Free app, GPLv3, no hidden premium tier [README].
• Privacy-first. No analytics, no third-party requests — your links go directly to your server [README].
• Share intent works. The core value proposition — share a link from anywhere on Android — does what it says [2][README].
• SSO compatible. Works with enterprise-grade Linkwarden setups using single sign-on [2].
• F-Droid distribution. For privacy-conscious Android users who prefer open-source app stores, this is a feature, not a limitation [README].
• v2.0.0 maturity. Default tags, tablet layout, improved UI — the app has reached a usable baseline [4].
• Actively translated. Weblate integration and multiple active translators suggest international community engagement [README].

Cons

• Thin client, not a full app. The Linkwarden interface you see in LinkDroid is the web UI in a WebView. This isn’t a native reading experience or native bookmark management — it’s a browser wrapper with a share button [README][3].
• No offline access. You need a live connection to your Linkwarden instance. If your server is down or you’re on a plane, the app doesn’t work [README].
• F-Droid only. Not on Google Play, and the developer has signaled it may stay that way. Users outside the F-Droid ecosystem face extra setup [README].
• Solo maintenance. One developer. The pace of updates and long-term maintenance are dependent on one person’s availability.
• Android only. No iOS equivalent under this project [README]. The Linkwarden team hinted at an official mobile app in development [2], but it hasn’t shipped yet.
• Dependent on Linkwarden’s API. Changes to Linkwarden’s authentication or API could break the app until the developer issues an update.
• 145 stars on the GitHub mirror. Small community relative to other self-hosted tools, meaning fewer third-party guides, fewer community troubleshooting threads.

---

Who Should Use This / Who Shouldn’t

Use LinkDroid if:

• You already self-host Linkwarden and want to save links from your phone without opening a browser.
• You’re on Android, use F-Droid (or are willing to), and value an app that doesn’t phone home to anything.
• You have an SSO-protected Linkwarden instance and need a mobile client that respects that setup.
• You save articles across multiple apps (Reddit, Twitter, news apps) and want one consistent share target.

Skip it if:

• You don’t already have Linkwarden running. Set up Linkwarden first — LinkDroid is an add-on, not a standalone product.
• You’re on iOS. There’s no equivalent under this project [README]. An iOS shortcut is a workaround [2], but not a proper app.
• You need a native reading experience with font controls, highlight support, and annotation. That’s Linkwarden’s web UI feature set, not something LinkDroid adds on top [3].
• You’re only on Google Play and won’t install F-Droid. The app isn’t there and may not come [README].
• You want an actively-staffed mobile client with enterprise SLAs. This is a community project.

---

Alternatives Worth Considering

LinkGuardian — another Android app for Linkwarden, available via IzzyOnDroid on F-Droid. Users in the Lemmy community have used both and some prefer LinkDroid, but LinkGuardian is a legitimate alternative if you want to compare [2].

iOS Shortcut — at least one Linkwarden user built an iOS shortcut that posts links to their instance via the share sheet [2]. Not a native app, but functional for iPhone users.

Linkwarden’s official mobile app — the Linkwarden maintainer teased an official mobile app in the Lemmy thread [2]: “Just wait till you hear about the upcoming official mobile app!” No release date was given, but if an official app ships, it would presumably replace third-party clients for most users.

Linkwarden browser extension — for desktop-first workflows, the browser extension does the same job as LinkDroid but for Chrome/Firefox/Safari. Not mobile, but worth knowing about if mobile isn’t your primary save method.

Karakeep (formerly Hoarder) — a competing self-hosted read-it-later tool with its own mobile app. The XDA reviewer [3] tested it alongside Linkwarden and found Linkwarden superior overall. If you haven’t committed to Linkwarden yet and want a system with a more integrated mobile story, Karakeep is worth evaluating.

Readeck — another self-hosted read-it-later option with a PWA that almost supports share intent on Android. The Codeberg issue thread [5] shows an active discussion about adding share target support to Readeck’s PWA; contributors have pointed to LinkDroid as a reference implementation for how to solve this problem.

---

Bottom Line

LinkDroid is a useful, unglamorous utility. It does one thing — give Android’s share menu a direct path to your Linkwarden instance — and it does that thing reliably. The v2.0.0 release added enough polish (default tags, tablet support, browser-open option) that it no longer feels like a prototype. If you’re already on Linkwarden, installing it takes ten minutes and meaningfully improves daily use.

The ceiling is also clear: this is a companion app, not a replacement for a native mobile client. You’re getting a share button and a web view. The reading experience, the organization interface, the search — all of that lives in Linkwarden’s web UI, not in anything LinkDroid builds on top. For users who want a true native mobile reading experience, the wait continues. For users who just want their links to stop living in browser tabs, LinkDroid is exactly enough.

---

Sources

1. idroot.us — “How To Install Linkwarden on Linux Mint 22”. https://idroot.us/install-linkwarden-linux-mint-22/
2. lemmy.world — “Linkwarden v2.12 - open-source collaborative bookmark manager” (community thread with user reports on LinkDroid). https://lemmy.world/post/35086101
3. Parth Shah, XDA Developers — “I finally found the perfect self-hosted read-it-later app to replace Pocket” (Jul 29, 2025). https://www.xda-developers.com/tested-several-read-it-later-apps-this-self-hosted-option-is-best/
4. selfh.st — “This Week in Self-Hosted (20 December 2024)” — LinkDroid v2.0.0 release notes. https://selfh.st/weekly/2024-12-20/
5. codeberg.org — “#180 - PWA: add url and share intent - readeck/readeck” (references LinkDroid as implementation reference). https://codeberg.org/readeck/readeck/issues/180

Primary sources:

• GitLab repository (canonical): https://gitlab.com/Dacid99/linkdroid-for-linkwarden
• GitHub mirror: https://github.com/dacid99/linkdroid-for-linkwarden
• F-Droid listing: https://f-droid.org/packages/com.sbv.linkdroid/