If “Share via Link” is missing from ZimaOS Files, first check your ZimaOS version before assuming the feature is unavailable in Community Edition. The source report came from 1.5.3-beta1, when a community reply said developers had temporarily disabled the feature for improvements and stability work.
That limitation is no longer the current state. ZimaOS now has an official 2026 “Share via Link” document describing the feature and its WebTorrent-based peer-to-peer transfer model. On a current stable release, a missing option should therefore be treated as a version, UI, file-type, or feature-state problem rather than an inherent Community Edition limitation.
What the Old Beta Issue Looked Like
The user could right-click a folder and see Share via Samba, but Share via Link was absent. The system was running 1.5.3-beta1 Community Edition.
A community reply said developers had disabled the link-sharing feature temporarily. The thread did not show an IceWhale staff confirmation in that conversation, so that historical explanation should be labeled community information rather than an official release statement.
Share via Link Is Documented Again on Current ZimaOS
The current ZimaOS Share via Link guide describes creating a special link from ZimaOS and transferring data using WebTorrent technology.
ZimaOS v1.2.5 release documentation also records the original addition of Share via Link, so the feature has existed historically even though later beta builds could temporarily disable it.
Step 1: Update to a Current Stable ZimaOS Release
Do not troubleshoot a missing beta feature indefinitely. Check Settings for your exact version and move to a current stable release after backing up important data.
If you intentionally run a beta channel, understand that experimental builds can temporarily remove or change UI features.
Step 2: Test the Right-Click Menu on a Simple File
Create or select a small ordinary file in your local ZimaOS storage and open its context menu. Testing a simple local file removes variables such as network storage permissions, special folders, or unsupported item types.
If Share via Link appears there but not on a particular mounted folder, the issue is scoped to that location or item rather than the entire system.
Step 3: Hard-Refresh the Files Interface
After an update, stale browser assets can leave old menus visible. Use a hard refresh or a clean private browser session, then open Files again.
If one browser shows the option and another does not, the server feature is probably present and the problem is frontend state.
Understand What Share via Link Actually Does
Current ZimaOS documentation says the feature uses WebTorrent-based peer-to-peer transfer rather than uploading your file to a central storage service first. That changes the privacy and availability model.
The official documentation warns that shared content may continue to circulate once distributed and recommends considering privacy, copyright, and security before creating a public link.
Share via Link vs Share via Samba
| Feature | Best use |
|---|---|
| Share via Samba | Ongoing authenticated access from Windows, macOS, Linux, and LAN/remote clients |
| Share via Link | Sending a specific file or folder through a generated link without creating a Samba account for the recipient |
The ZimaOS sharing guide provides additional network-sharing context.
FAQ
Is Share via Link unavailable in Community Edition?
The 2025 beta thread does not establish that. Current ZimaOS documentation treats Share via Link as an available feature, so check your version and current UI first.
Why did the option disappear in 1.5.3-beta1?
A community reply said it had been temporarily disabled for improvements and stability. The thread did not contain an official staff confirmation of the exact reason.
Does Share via Link upload my file to Zima's cloud?
The current official guide describes a WebTorrent-based peer-to-peer model rather than central file storage.
Should I use Share via Link for private documents?
Only after understanding the link and P2P exposure model. For sensitive ongoing access, authenticated Samba or a private remote-access path may be more appropriate.
