Tizen Studio Is Deprecated: What Samsung TV Developers Need to Know
Verified as of 1 August 2026. Tooling versions in this space move fast — check the linked sources before acting on anything here.
If you build apps for Samsung Smart TVs, the IDE you have been using for the last decade is on its way out. The Tizen SDK team has formally deprecated Tizen Studio, and the Visual Studio Code extension is now the primary, officially supported development environment.
This is not a rumour or a community reading of the tea leaves. Samsung published a deprecation notice, added a warning popup inside Tizen Studio itself, and stated that all new feature development now happens exclusively in the VS Code environment.
Here is what actually happened, when it happened, and — the part most coverage is getting wrong — why you probably do not need to panic-migrate this week.
The short version
- Tizen Studio is deprecated starting with Platform 10, SDK 6.5.
- The Tizen Extension for Visual Studio Code is the designated replacement, and Samsung says it covers all Tizen Studio functionality plus additional features.
- Visual Studio (the Windows-only tooling) is being consolidated away in the same move.
- Dynamic Analyzer is being deprecated alongside Tizen Studio.
- Tizen Studio still works today, and Samsung’s TV division is still shipping TV Extension images built for it.
How we got here: 2016 to 2026
The arc has a clear shape. Samsung spent a decade consolidating its tooling into one IDE, then abandoned the IDE and kept the consolidation.
2016 — the Tizen SDK becomes Tizen Studio
Before Tizen Studio existed, every Tizen platform version had its own SDK. Developers targeting multiple platforms had to install multiple SDK programs, which was painful to maintain and slow to update.
On 1 September 2016, Samsung’s answer shipped: the Tizen SDK was renamed and rebuilt as Tizen Studio 1.0, updated from Tizen 2.4, with a new UX and Eclipse upgraded from Kepler (4.3) to Mars (4.5.2). One installer now let you select the platforms and profiles you needed. Platform and SDK release notes were split from that point onward.
2017–2024 — the Eclipse maintenance treadmill
Tizen Studio 2.3 moved from Eclipse Mars to Oxygen, updated CDT to 9.3.2, and migrated the debugger from CDI to DSF. Steady work, all of it spent keeping an Eclipse fork alive rather than improving the actual development experience.
Meanwhile, Samsung was quietly running three IDEs in parallel: Tizen Studio on Windows, macOS and Linux; Visual Studio on Windows only; and VS Code on all three. On the TV side there was also an Atom extension, which died when GitHub discontinued Atom — with VS Code named as the replacement offering similar functionality.
March 2025 — the strategy flips
Announced as part of Tizen 9.0, Samsung described a modernized development environment centred on VS Code: lightweight, fast, and aligned with current development trends, providing a smoother experience than the Eclipse-based Tizen Studio. The commitment was explicit — maintenance of Tizen Studio would continue through the end of 2025, but all new feature development would focus exclusively on VS Code.
Tizen Studio 6.1 — the warning shot
Version 6.1 was where the deprecation became visible to everyone. Tizen app samples and the Web Add-on template were deprecated, log4j was bumped from 1.2.17 to 2.24.3, and — most significantly — a notification popup was added warning of the deprecation of Tizen Studio and Dynamic Analyzer in the next version.
That Dynamic Analyzer mention is worth pausing on. It is not being relocated into VS Code. It is being retired.
Platform 10 / SDK 6.5 — the formal notice
The Tizen SDK team’s official announcement confirms deprecation begins with the next SDK release. The stated reasoning is refreshingly blunt: new features were increasingly being developed exclusively for VS Code because of Tizen Studio’s limitations, so the team decided to make the Tizen Extension for VS Code the primary IDE.
Samsung also committed to migration support — a feature-by-feature comparison guide covering installation, views and menus, plus video guides on reusing existing Tizen Studio projects in VS Code. At the time the notice was published, these were described as “will soon be available,” which is worth keeping in mind if you go looking for them.
The catch nobody is mentioning
Here is the nuance that separates an accurate picture from a headline: Samsung’s TV division has not fully followed the platform division.
TV Extension Image 10.0.0 shipped on 26 February 2026 for Windows, Ubuntu and macOS — with Chromium upgraded to M130, .NET 8 and TizenFX TV API 12.12.0, and 32-bit emulator images deprecated. That is a Tizen Studio extension. Samsung’s Smart TV documentation still carries a full Tizen Studio section, TV Extension download, archive and release-history pages, and a Tizen Studio FAQ, sitting alongside the newer VS Code pages.
So the accurate framing is this: the IDE is deprecated, the SDK underneath it is not, and the TV emulator images are still being cut against the deprecated shell.
The community read matches. As one widely-used TV project’s install guide puts it, Tizen Studio remains functional and usable for building and installing applications, but should be treated as a legacy tool — no longer actively maintained, and potentially subject to removal.
Should you migrate right now?
Depends entirely on where you sit.
Migrate now if you are starting a new project, onboarding new developers, or want the tooling that only exists on the new side. The VS Code path has genuinely better first-run ergonomics, and there are capabilities there — including an AI/MCP integration — that will never be backported to Eclipse.
Wait if you have a working Tizen Studio pipeline, a signed certificate chain you do not want to touch, and a shipping deadline. Nothing breaks the day SDK 6.5 lands. What you lose by waiting is access to new features, not the ability to build.
Plan regardless if you depend on Dynamic Analyzer. That one has no direct successor, and it is worth working out your replacement profiling story before it disappears.
One more practical note: the documentation itself has moved. docs.tizen.org and developer.tizen.org now redirect to a rebuilt portal at samsungtizenos.com. A lot of the Stack Overflow answers and blog posts you have bookmarked point at URLs that now bounce.
What’s next in this series
This post is the status update. The practical material lives in its own posts:
- Migrating from Tizen Studio to VS Code: a complete setup guide — the two extensions, publishers, CLI install, certificates, and the failure modes you will hit
- What Samsung gains and what developers lose — the trade-offs, honestly assessed
- Samsung’s Tizen MCP Server — conversation-driven TV development, tested on real hardware
- Samsung TV development on Apple Silicon — the emulator situation, and what actually works