# Apps2Samsung: sideloading Tizen apps onto Samsung TVs without Tizen Studio > Apps2Samsung is a cross-platform tool, written in C#, that installs .wgt and .tpk apps on Samsung Tizen TVs from Windows, Linux, macOS or Android. It handles certificate signing, device detection and the community catalog of 49 or more apps, but it depends on the TV having Developer Mode enabled. **Apps2Samsung/Apps2Samsung** — One-click app installer for Samsung TVs, projectors and smart monitors (Tizen) — Jellyfin, Moonlight, and the whole community catalog. - Repository: https://github.com/Apps2Samsung/Apps2Samsung - Website: https://www.apps2samsung.com - Stars: 2,177 · Forks: 68 - Language: C# - License: MIT - Published: 2026-10-09 · Updated: 2026-10-09 · Language: en - Canonical page: https://hysenlabs.com/projects/apps2samsung-apps2samsung ## Samsung Developer Mode is a prerequisite the tool cannot waive Sideloading onto a Samsung TV requires the television to be in Developer Mode first. Apps2Samsung automates the certificate and installation steps, but enabling Developer Mode is a step you do on the TV itself, not in the tool. When the tool connects and something is wrong, it tells you specifically what the problem is rather than returning a generic error. Four conditions are named: Developer Mode is off, the IP address is wrong, the IP is reversed, or the TV needs a power cycle. Getting a named condition rather than a raw TCP timeout is the practical difference from attempting a manual connect. Developer Mode is a Tizen platform feature. Samsung controls how it is exposed, and the exposure has changed across model generations. One boundary stated plainly in the project: Orsay-based TVs, those manufactured before 2015, are no longer supported. Apps2Samsung runs only against Tizen OS, which covers the Samsung smart TV line from 2015 onward as well as Tizen-based projectors and smart monitors. Verify your TV's firmware before installing the tool on your computer. ## Certificate signing reduces to a one-time account sign-in Getting an app onto a Samsung TV manually requires a signing certificate, and working through Tizen Studio's certificate manager is where most users stop. Apps2Samsung reduces that to a Samsung account sign-in. From that sign-in it derives and stores the certificate, then applies it on subsequent installs to the same TV without prompting again. For a household with multiple televisions, a DUID (device unique identifier) can be entered in advance to pre-authorize a TV before connecting to it physically. That removes the need for a separate sign-in flow for each set. When an app requires restricted access, the tool selects between Public and Partner certificate types without asking the user. The project does not list which catalog apps require the Partner type, so you cannot tell before starting which installs will invoke it. There is also a gap that applies over time: if the Samsung account used for signing is deleted or its password changes, the stored certificate becomes invalid. How to recover from that situation is not described anywhere the README links to. ## Installing on Arch Linux, other Linux distributions, NixOS and Android On Arch Linux the AUR package is the straightforward path. The project publishes it through its own release workflow, so it follows every stable release automatically: ```sh yay -S apps2samsung ``` Alternatively, `paru -S apps2samsung` installs the same package. Both x86_64 and aarch64 architectures are covered, with the same build as the .deb and .rpm releases. Other Linux distributions can use the .AppImage, .deb, .rpm or .tar.gz from the GitHub releases page. On NixOS, cloning the repository and running `nix-shell` is the path the project gives; the shell environment builds and launches the tool automatically. Three Android install paths exist. Obtainium can track the GitHub repository directly and pull updates when a new stable is published. For F-Droid, Droid-ify and Neo Store users, the custom repository is available by adding `https://apps2samsung.com/fdroid/repo` through the app's Settings, Repositories, Add flow. The direct alternative is to download the `-android.apk` from any release page entry and sideload it. Windows and macOS releases appear on the releases page but the project does not describe a package manager path for those platforms. ## The community catalog and the .wgt and .tpk install path The community catalog at github.com/Apps2Samsung/tizen-community-packages holds 49 or more apps, and Jellyfin, Moonlight, Moonfin, Litefin and TizenTube are among them. These are apps that Samsung's official app store does not distribute. That gap is the main reason the tool exists. Both .wgt (Tizen web app package) and .tpk (Tizen native package) formats are accepted by the installer. Bringing your own .wgt file is a supported path, and the same install interface handles it alongside catalog entries. Developers building Tizen web apps and wanting to test on physical hardware can use it without adopting any catalog app at all. The 49 or more figure is a lower bound, not a final count. Community-shared and older .wgt builds that fall outside the main catalog are kept in the same repository under a separate section. Individual compatibility with a specific Tizen firmware version is not documented for any catalog entry: neither the README nor the catalog repository maps apps to Tizen version requirements, so testing on your actual TV firmware is the only way to verify. ## Jellyfin configuration at install time covers server address, themes and playback options Jellyfin is the most common reason to use Apps2Samsung, and the tool handles several Jellyfin settings during installation rather than leaving them for after the app is on the TV. Before running the install, you set the server address and auto-login credentials. JellyThemes and custom CSS can be injected at this stage, which means the theming is applied from the first launch rather than requiring a manual setup inside the app. Playback preferences, server plugin configuration and a fix for the YouTube trailer feature are also configurable at install time. TVapp channels are settable here as well. The YouTube trailer fix being a separate toggle implies it requires a code-level patch rather than a configuration value inside Jellyfin itself. Custom launcher icons and titles are set before the install runs, not edited on the TV afterward. This is useful when installing for someone else and wanting the launcher to show a specific name. One unanswered question across all of these options: the project does not state which Jellyfin server version they target. If a server update removes or renames a setting, whether the corresponding option in Apps2Samsung breaks silently is not described. ## TV remote mode and the diagnostic access it does not share Apps2Samsung includes a remote control mode that operates over Samsung's own remote channel without requiring Developer Mode, making it usable on TVs that are not yet configured for sideloading. Navigation covers the D-pad, playback, volume, channel switching and power, with live typing added for sending keystrokes from the computer to text input fields on the TV. Diagnostic access is a different set of permissions and requires Developer Mode to be enabled. It reads the DUID, Tizen firmware version, model identifier and current Developer Mode state. A log console streams TV output live, and saving that stream to a file is an option. App debugging routes the Tizen web inspector to chrome://inspect on the connected computer. Moving a setup to a different machine involves exporting settings and signing certificates to a single file, which can then be imported on the new machine. App management covers listing installed apps with their icons, plus uninstall, launch, stop, debug and force-remove. Force-remove is the path for packages a normal uninstall leaves behind, though the project does not describe the conditions that cause an ordinary uninstall to leave residue. ## Network limits and the dependency on Samsung controlling Developer Mode Pre-2015 Orsay TVs are not supported, and this is stated without qualification. Beyond that firmware line, the tool requires the device running it to reach the TV's IP address on the same network segment. Automatic scanning handles the typical home network, and a manual IP entry exists for cases where scanning fails. NAT traversal, VPN configurations and firewall rules between subnets are not addressed. The tool connects at install time and does not run persistently on the TV. DHCP reassignment after a prior install would require entering the updated IP on the next session. Installing the same app on multiple TVs simultaneously is not described anywhere in the README. A dependency worth considering: the sideload mechanism depends on Samsung continuing to expose Developer Mode in a form that the tool can use. If a firmware update changes how Developer Mode works or restricts which devices can connect, Apps2Samsung would need to adapt. This has already happened once in the history of Samsung TV sideloading, before Apps2Samsung existed. It is not a near-term prediction; it is a category of risk specific to tools that depend on undocumented or semi-official platform access. ## Stable v2.8.1 and beta v2.8.2-beta, with the default branch tracking the beta line Stable v2.8.1 was published 2026-09-23, and v2.8.2-beta followed one day later on 2026-09-24 carrying features not yet in the stable channel. The last push to the repository was 2026-10-05. An in-app updater with an optional beta channel opt-in means updates do not require returning to the releases page once the tool is installed. The default branch is named beta rather than main, so the repository's default view reflects current development state and is not pinned to the most recent stable release. Cloning without specifying a tag pulls beta-channel code. Anyone who wants the stable build should target the v2.8.1 tag explicitly. The project is MIT-licensed, with a NOTICE.md file in the repository root covering additional attribution. The C# source spans Apps2Samsung.Core/, Apps2Samsung.Mobile/ and Jellyfin2Samsung-CrossOS/ at the top level, alongside fastlane/ and fdroid/ directories that handle the Android release pipeline. Translation into 30 languages is managed through Crowdin at crowdin.com/project/jellyfin2samsung, and the tool starts in the system language by default. Switching languages is available at any time after launch, without reinstalling. ## Conclusion Apps2Samsung is worth adopting if you own a Tizen-based Samsung TV and want to run Jellyfin or another catalog app that Samsung's store does not carry. Certificate handling and the community catalog of 49 or more apps remove the friction of manual Tizen Studio sideloading. Skip it if your TV is a pre-2015 Orsay model, since those are explicitly excluded. Before committing, confirm that your TV's firmware accepts Developer Mode, because the tool reports exactly what is wrong when it cannot connect, but you still have to fix the problem on the television side. ## FAQ ### Does Apps2Samsung work without Tizen Studio? Apps2Samsung handles device detection, certificate signing through a Samsung account sign-in, and app installation directly, with no Tizen Studio installation required. It replaces the Tizen Studio certificate workflow rather than depending on it. ### How do I install Apps2Samsung on Linux? On Arch Linux, the AUR package installs with yay -S apps2samsung or paru -S apps2samsung, covering x86_64 and aarch64. Other Linux distributions can use the .AppImage, .deb, .rpm or .tar.gz from the releases page. NixOS users can clone the repository and run nix-shell. ### Which Samsung TVs does Apps2Samsung support? Apps2Samsung works with Samsung TVs, projectors and smart monitors running Tizen OS. Pre-2015 Orsay-based TVs are explicitly not supported. The TV must also have Developer Mode enabled before any installation can proceed. ### Can I install my own .wgt file with Apps2Samsung? Yes. The tool accepts both .wgt (Tizen web app) and .tpk (Tizen native) files alongside its built-in community catalog. A local .wgt can be selected through the same install interface as any catalog entry. ### Is Apps2Samsung available for Android phones? Yes. The Android app can be installed through Obtainium by adding the GitHub repository URL, through the custom F-Droid repository at apps2samsung.com/fdroid/repo, or by sideloading the -android.apk file from the GitHub releases page. ## Sources - [Apps2Samsung/Apps2Samsung on GitHub](https://github.com/Apps2Samsung/Apps2Samsung) - [License: MIT](https://github.com/Apps2Samsung/Apps2Samsung/blob/beta/LICENSE) - [Project website](https://www.apps2samsung.com) - [README](https://github.com/Apps2Samsung/Apps2Samsung/blob/beta/README.md) - [Releases](https://github.com/Apps2Samsung/Apps2Samsung/releases) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/apps2samsung-apps2samsung