Custom Provider

Subify Custom Provider: Configure a Custom API

How to set up a custom Provider in Subify: service address, model and API key for supported workflows.

ChromeChromeFirefoxFirefoxChrome & Firefox
01
subify
01What is a Custom Provider?
Custom Provider

What is a Custom Provider?

Use this path to connect a service you choose in the settings.

02
subify
02Endpoint & Model
Custom Provider

Endpoint & Model

The service address and model must match the format Subify expects.

03
subify
03API Key
Custom Provider

API Key

Keep your key only in an environment you trust, and never post it in a public issue or chat.

04
subify
04Connection Test
Custom Provider

Connection Test

After setup, run a short translation to check the connection.

FAQ

Key Answers About Custom Providers

We collected the common questions for this section so you can find answers without jumping between pages.

For users who want more control over the API or Provider they use.
No. The service must support the format and features the Subify workflow needs.
In the current version, the key and Provider settings are stored in local browser storage.
Check the endpoint, key, model name and response format of the service, one by one.
Depending on the workflow and settings, translation and audio may use separate Providers.
In the current version, local settings and Provider keys stay in the browser and are not sent to a Subify server.
Subify

A video in another language can still be watched

Install Subify and enable translation, captions, or dubbing alongside your viewing experience.