How to Customize IINA with Settings and Plugins

Updated

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

Need Use settings Use a plugin
Hide or rearrange controls and sidebars Yes Not needed
Match macOS gestures and system features Yes (built in) Not needed
Add new subtitle sources No Yes
Add video tools or new interfaces No Yes
Avoid installing third-party code Yes No

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.