iina.io

No. According to IINA's official site, the player "does not include tracking or telemetry." That statement is the direct answer for anyone deciding whether to install it: IINA is presented as a media player that does not phone home with usage data. The rest of this page explains what that claim covers, how you can verify it, and where the limits of the claim lie.

What the official statement says

The relevant line on iina.io appears under the "Free and open-source" heading:

"IINA is free and open source, built on mpv and maintained by its community. It does not include tracking or telemetry."

Two things are being asserted together, and they matter for different reasons:

• No tracking or telemetry — the app is not described as collecting or transmitting usage analytics.
• Free and open source, built on mpv — the code is publicly available, which is what makes the first claim checkable rather than just a promise.

Why "open source" is the part that makes the privacy claim verifiable

A closed-source app can claim it collects nothing; you have to take that on trust. IINA's privacy statement is different in kind because the source is public. The site explicitly invites participation through GitHub, which means the same repository that holds the code is where you can inspect what the app does.

Practical ways to check for yourself:

1. Read the source on GitHub. Look for networking code, analytics SDKs, or HTTP requests that aren't tied to a user-initiated action (like loading a subtitle or stream you asked for).
2. Watch outbound connections. Run IINA and monitor network activity with a firewall or network monitor. A player that only connects when you open a network stream or fetch subtitles behaves very differently from one that pings a server on launch.
3. Check the release notes and issue tracker. Privacy-relevant changes tend to surface in release notes or community discussion, and the site links to both.

What the claim does not cover

The site's statement is about IINA itself. It does not automatically extend to everything around it:

• Plugins. IINA supports community-built plugins that can add subtitle sources, video tools, and new interfaces. A plugin that fetches subtitles from an online service will make network requests — that behavior belongs to the plugin, not to IINA's core. If privacy is your concern, treat plugins as separate software and review them individually.
• Network streams and subtitle downloads. When you open a URL or download subtitles, IINA connects to those servers because you asked it to. That's expected behavior, not telemetry.
• The website and downloads. The statement covers the app. It says nothing about analytics on iina.io itself, so don't read it as a claim about the website.

The short version

If your reason for asking is "can I install this without it reporting back on what I watch," the official position is that it does not. If your reason is "I want to be certain," the open-source code is the evidence — and that's the strongest form of answer a privacy question like this can get.

An open-source UI element library is a collection of individual, ready-made interface pieces—buttons, cards, inputs, toggles, loaders—that you copy into your own project and adapt. A UI framework, by contrast, is a structured system of components, conventions, and often a theming layer that governs how your whole interface is built. The practical difference: an element library gives you a snippet; a framework gives you a way of working. If you need a polished button in ten minutes, reach for the element library. If you're building a 40-screen product with a team, you probably want the framework.

What "open-source UI element library" actually means

The term gets used loosely, so it helps to separate the parts:

• Open-source: the code is publicly available, and the license tells you what you may do with it—copy, modify, redistribute, or use commercially.
• UI element: a single, self-contained piece of interface, usually small enough to read in one sitting. A button with hover states, a pricing card, a search field.
• Library: a browsable, searchable collection of those elements, typically contributed by many different people.

On a site like Uiverse, elements are shared by a community and written in plain CSS or Tailwind. You find one you like, copy the markup and styles, paste them into your project, and adjust colors, spacing, and text to fit. There's no package to install and no build step required—which is exactly the appeal, and also the source of most of the confusion.

Element library vs. UI framework: the core differences

The table isn't a verdict. It's a map of trade-offs. Element libraries win on speed and freedom; frameworks win on consistency and maintenance.

Licensing and attribution: what to check before you paste

This is where people get into trouble, and it's worth slowing down for.

1. Find the license. Every element or collection should state one. Common open-source licenses include MIT, Apache-2.0, and BSD. Some projects use copyleft licenses like GPL, which can impose obligations if you redistribute your code.
2. Understand what the license permits. MIT and Apache-2.0 are permissive: you can typically use the code in commercial and closed-source projects. Copyleft licenses may require you to release derivative source under the same terms.
3. Check attribution requirements. Permissive licenses usually require you to keep the copyright notice and license text somewhere in your project. That's a real obligation, not a formality.
4. Look for per-element terms. On community sites, the site's overall terms and the individual contributor's stated wishes may differ. If a contributor asks for credit, honor it.
5. When in doubt, ask or avoid. If a snippet has no license at all, you don't have clear permission to reuse it. Treat "no license" as "not open source," even if the code is publicly visible.

This article is general information, not legal advice. For commercial products with real exposure, have someone qualified review the licenses you're relying on.

How to use a community element in your project: a practical workflow

Here's a repeatable process that avoids most of the usual mess.

1. Start from a real need, not a browsing session

Decide what you need first—"a compact primary button with a loading state"—then search. Browsing aimlessly produces a pile of pretty snippets that don't fit together.

2. Copy the smallest version that works

Take the markup and the styles. Strip anything you don't need: demo wrappers, extra animations, decorative layers. Less code means fewer surprises.

3. Convert it to your conventions

If your project uses design tokens or CSS variables, replace hard-coded values:

/* Before: hard-coded */
.button { background: #4f46e5; border-radius: 8px; }

/* After: token-based */
.button { background: var(--color-primary); border-radius: var(--radius-md); }

This one step is what keeps a copied element from looking like a foreign object in your UI.

4. Check accessibility before you ship

Community elements vary widely here. Verify at minimum:

• Keyboard focus is visible and the element is reachable by Tab.
• Color contrast meets WCAG AA (4.5:1 for normal text).
• Interactive elements use semantic HTML (<button>, not a clickable <div>).
• Form inputs have associated labels.
• Motion respects prefers-reduced-motion.

5. Test in context

Paste it into a real page with real content. Long labels, small screens, and dark mode break more copied elements than anything else.

6. Note where it came from

Keep a short comment or an internal credits file: source, license, date. Future you—and your legal reviewer—will be grateful.

Where element libraries genuinely shine

• Prototypes and demos: you need something clickable today, not a design system.
• Landing pages and marketing sites: a handful of distinctive elements, each custom.
• Filling gaps: your framework lacks one specific component, and you don't want to build it from scratch.
• Learning: reading well-made CSS is one of the fastest ways to improve.
• Small projects: a personal site doesn't need a theming architecture.

Where they fall short

• Consistency at scale: ten elements from ten contributors rarely look like one product.
• Maintenance: you own every copy. When your design changes, you edit each one.
• Accessibility debt: you inherit whatever the contributor did or didn't do.
• No upstream fixes: a bug fixed in the original won't reach your copy.
• Integration friction: different naming conventions, different units, different assumptions about resets.

When to choose which

Choose an element library when the scope is small, the timeline is short, or you need a few distinctive pieces rather than a whole system.

Choose a framework or design system when multiple people build multiple screens over months, when consistency is a product requirement, or when accessibility and theming need to be guaranteed rather than checked.

A hybrid works well for many teams: adopt a framework for the structural components—forms, navigation, layout—and borrow individual elements for the places where you want personality. Just route every borrowed element through the same token and accessibility checks, so it lands as part of your system rather than beside it.

The short version: open-source UI element libraries are a fast, flexible way to get good-looking interface pieces into a project. They are not a substitute for a design system, and the license and accessibility details are the part worth reading carefully.

IINA is a free, open-source media player built specifically for macOS. It is designed as a native macOS app rather than a ported cross-platform tool, and it is built on mpv, the open-source media playback engine. If you watch local video files on a Mac and want something that behaves like a first-class macOS application — with trackpad gestures, Picture in Picture, and system media controls — IINA is aimed at exactly that use case. The current download listed on its site is version 1.5.0, which requires macOS 12.0 (or macOS 11.0 on Intel machines).

What makes IINA different from a generic media player

Most media players that run on macOS are cross-platform applications with interfaces adapted to the Mac. IINA takes the opposite approach: it is built as a macOS app from the start, so its behavior follows conventions Mac users already expect.

According to the project's own description, that includes:

• Trackpad gestures for navigation and control
• Media controls integrated with the system
• Picture in Picture for floating video playback
• Live Text, which lets you select text visible inside a video frame

The practical difference is that these features come from the operating system rather than being reimplemented. For example, Picture in Picture behaves like PiP in Safari or QuickTime, and media keys work the way they do for other native apps.

Customization and plugins

IINA treats interface layout as a personal preference. The site states that you can adjust its controls, sidebars, and other interface items to match how you use it. Beyond built-in settings, a plugin system lets the community extend the player with:

• Additional subtitle sources
• Video tools
• New interfaces
• Other features contributed by third parties

There is separate documentation aimed at plugin developers, so if you want to build an extension rather than just use one, that is the entry point.

Free, open source, and no tracking

IINA is free and open source, built on mpv and maintained by its community. The project states that it does not include tracking or telemetry — a meaningful distinction if you prefer software that does not report usage data.

Because it is community-maintained, there are several ways to participate beyond just using it:

Who should consider IINA

IINA fits you well if you:

• Watch local media files on a Mac and want native macOS behavior
• Care about open-source software with no telemetry
• Want to extend your player through plugins or custom subtitle sources
• Prefer an interface you can rearrange to your own habits

It is less relevant if you mainly stream from subscription services, since those are typically handled by dedicated apps or browsers rather than a general-purpose player. And because the download page lists specific macOS version requirements, check that your system meets them — macOS 12.0, or macOS 11.0 if you are on an Intel Mac — before downloading version 1.5.0.

IINA can be customized in two ways: through built-in interface settings that adjust controls, sidebars, and other UI elements, and through community plugins that add features like subtitle sources, video tools, and new interfaces. The settings route requires no extra downloads, while plugins require finding and installing them from the IINA plugin ecosystem. Both are available to any IINA user on a supported macOS version.

Adjusting the Interface Without Plugins

IINA is designed as a native macOS app, so its customization options follow that philosophy. According to the IINA site, the player "lets you adjust its controls, sidebars, and other interface items to suit the way you use it."

In practice, this means you can rearrange or hide on-screen controls, change which sidebars appear and what they contain, and adapt the layout to how you actually watch video. The exact set of toggles lives in IINA's preferences, and because the app is built to feel at home on macOS, it also inherits system-level behaviors such as trackpad gestures, media controls, Picture in Picture, and Live Text.

A reasonable starting point:

1. Open IINA's preferences and review the interface-related sections.
2. Toggle sidebars and control visibility to match your viewing habits — for example, hiding controls you never use to get a cleaner window.
3. Test with a real video file to confirm the layout behaves as expected during playback.

The goal is a setup where the controls you need are reachable and the ones you don't aren't in the way.

Extending IINA with Plugins

Plugins go beyond interface tweaks. The IINA site states that plugins "can extend it further, adding subtitle sources, video tools, new interfaces, and other features created by the community."

That covers a wide range of additions:

• Subtitle sources — pull subtitles from providers beyond what's built in.
• Video tools — add processing or analysis features to your playback workflow.
• New interfaces — replace or supplement parts of the UI with community-designed alternatives.

Plugins are created by the community rather than the core team, so availability and quality vary by plugin. The IINA website has a plugin exploration page where you can browse what exists, and there is separate documentation aimed at plugin developers if you want to build your own.

Installing a Plugin

The general flow is:

1. Browse the plugin listings on the IINA site to find one that matches your need.
2. Follow that plugin's own installation instructions — IINA's site points users to the plugin ecosystem rather than bundling plugins into the app.
3. Restart or reload IINA if required, then verify the plugin's feature appears where expected.

Because plugins are third-party, check what a plugin does before installing it, especially if it requests access to files or network resources.

Settings vs. Plugins: Which to Use

If your goal is a cleaner or differently arranged player, settings are enough. If you need functionality IINA doesn't ship with, a plugin is the path.

What to Know Before You Start

IINA is free and open source, built on mpv and maintained by its community. The site notes it does not include tracking or telemetry. The current download listed is version 1.5.0, which requires macOS 12.0, or macOS 11.0 on Intel machines — so confirm your macOS version before installing or updating.

If you want to go further than using plugins, the project accepts contributions in several forms: reporting issues, suggesting features, contributing code on GitHub, translating on Crowdin, and supporting with donations. Plugin authors have their own documentation to work from.

The practical takeaway: start with the built-in settings to shape the interface around how you watch, then add plugins only for capabilities you actually need.

IINA 1.5.0 requires macOS 12.0 or later. On Intel Macs, the minimum is macOS 11.0. IINA is built specifically as a macOS app, so it does not run on Windows, Linux, or other operating systems.

Version and OS requirements

The distinction matters because the requirement is not identical across hardware. If you are on an Intel Mac running macOS 11.x, IINA 1.5.0 is still within range. If you are on Apple silicon, plan for macOS 12.0 or later.

Checking your macOS version

1. Open the Apple menu in the top-left corner.
2. Choose About This Mac.
3. Read the macOS name and version number shown in the window.
4. Compare it against the table above.

Expected result: you can tell immediately whether your Mac meets the 12.0 (or 11.0 on Intel) threshold before downloading.

Platform limits

IINA is "designed as a macOS app," with an interface that uses system conventions such as trackpad gestures, media controls, Picture in Picture, and Live Text. That design focus is also the constraint: there is no stated support for non-macOS platforms. If your machine runs Windows or Linux, IINA is not an option.

Other things to know before installing

• Price: IINA is described as free and open source, built on mpv and maintained by its community.
• Tracking: The site states it does not include tracking or telemetry.
• Extensibility: Plugins can add subtitle sources, video tools, and new interfaces.
• Older macOS versions: If your Mac is below the stated minimum, the current 1.5.0 build is not intended for it. The site links to "More downloads," which is the place to check whether an earlier release fits your system.

Common sticking points

• Assuming one minimum applies to all Macs. The Intel minimum (11.0) is lower than the general one (12.0), so check which hardware you have.
• Downloading before checking the OS version, then finding the app will not launch.
• Expecting a cross-platform build. The macOS-only design is deliberate, not a temporary gap.