Global Tuber Manual | Color-Bullet YTT Subtitle Translation App

Q: What is the difference between API upload and manual upload?

YouTube_Upload\VIDEO_ID is for API upload. After_translation is for manual upload. The folder to check depends on which method you use.

Check

Check Before You Start

Check the supported environment, license requirements, and setup items before using Global Tuber.

Supported Environment

Global Tuber is a desktop app for Windows 10 / Windows 11.
There are no plans for a smartphone app.
A Mac app is under consideration.

What You Need Before You Start

Internet connection
Google account
YouTube Data API
DeepL API

Display Settings

In Global Tuber settings, you can change the design and display font. If the text is hard to read, adjust the display before you start working.

License

You must enter a license key the first time you start the app.
One license is required for each YouTube channel.
A separate license is required when using a different YouTube channel.

Using the app on more than one PC

You can use the same YouTube channel on more than one PC. To use the app on another PC, install it there using the same steps, then copy the program folder for the same channel if needed. You will need to enter the license key again the first time you start it.

Free Version and Paid Version

You can use the free version for 30 days.
The paid version is a one-time purchase license.
It works as long as the supported environment and external APIs remain available.
You can purchase the paid version after using the free version for at least three weeks.

DeepL Character Count

The DeepL character count shown by the app is an approximate reference. We are not responsible for the accuracy of the count shown in the app. For the exact character count, log in to DeepL and check it there.

Support Contact

The support email address is shown on the license authentication screen or in the email that sent your license key. The email address is not published on the public page.

1

Quick Start

First-time users can check the required preparation in four steps. The numbered sections below explain each item in detail.

Image explaining practice with a private test video

Start Here

Check basic setup, practice with a private test video, confirm output locations, and see where to look if something goes wrong.

1

Basic Setup

Turn on file extensions and complete the settings required to use the API.

View steps

2

Practice with a Private Test Video

Don't worry about making mistakes; that's what practice is for. Use a private test video of about five minutes and practice the end-to-end workflow from translation through upload several times. Check the workflow before using it with real channel videos.

View steps

3

Title, Description, and Subtitle Upload

Check the API files in YouTube_Upload\VIDEO_ID, or the files for manual upload in After_translation.

View steps

4

Details Only When Needed

Use the Task Guide, Troubleshooting, FAQ, and Details sections only when you need that information.

View details

If you are unsure, use Troubleshooting to check common causes and where to look. Go to troubleshooting

2

Complete Basic Setup First

Complete these minimum setup steps before trying translation and upload.

1

Show File Extensions

Open File Explorer (user folder)

Open a folder in Windows. You can use your user folder or any other folder for this check.

Select View in the top menu. Refer to the image below.

In Windows 11, open View from the top menu.

Select Show under the View menu. Refer to the image below.

Move the mouse over Show near the bottom of the menu that opens.

Check File name extensions

When extensions such as .json, .srt, .ytt, and .txt are visible, it is easier to identify file types.

If you cannot find this setting, search for "Windows show file extensions".

2

Rename `client_secret.json`

The authentication file downloaded for YouTube Data API has a long name. Rename it to the shorter name below.

Long file name immediately after downloadclient_secret_xxxxxxxx.apps.googleusercontent.com.json

Rename the fileclient_secret.json

Destination folderconfig\client_secret.json

Authentication will not work if the file still has the long downloaded name.

3

`channel_info.json` Channel ID and `default_language`

channel_info.json is the settings file for YouTube channel information. There are two versions: one for templates and one for API upload.

In the template, set only the channel ID and main language, and leave the other items blank. This section explains how to fill in the template.

Check the template locationYouTube_Upload\Templates\channel_info.json

Also check the save location for API uploadYouTube_Upload\channel_info.json

Check the channel ID

Open your YouTube channel. In the channel URL, the 24-character value that starts with UC after channel/ is the channel ID.

For multilingual global use, English (en) is recommended for default_language

For multilingual global use, even for channels outside English-speaking regions, set default_language to English (en).

This is due to how YouTube displays titles. If a title is not translated into the viewer's language, YouTube displays the title in the language set in default_language.

Using English as the default language helps viewers understand the content in regions where you have not prepared a translation.

For multilingual global use, English (en) is also recommended for the channel name default_language

For multilingual global use, also set the channel-name default_language to English (en).

Use a clear and short English channel name as the base.

Channel naming is important because it can strongly affect subscriber growth and revenue.

✔ Recommended methods (either option can work well)

Use one clear and short English channel name for all languages
Set default_language to English and use channel names translated into every language

❌ Not recommended (may slow growth)

Use a non-English channel name unchanged in every language
Use a channel name that mixes English and another language half and half

How to specify default_language for multilingual global use

YouTube_Upload\Templates\channel_info.json

Channel name and channel description template

Required fields: "channel_id" and "defaultLanguage". en is recommended.

"channel_id": "UCxxxxxxxxxxxxxxxxxxxxxx",
"defaultLanguage": "en"

* Leave the other fields blank.

YouTube_Upload\Templates\metadata.json

Video title and description template

Required field: "default_language". en is recommended.

"default_language": "en",

* Leave the other fields blank.

Setting default_language (main language) when not expanding globally

Enter the YouTube channel ID in channel_id.

In default_language, normally enter the code for the main source language.

Use the main language code from the YouTube-Code column in Translation-list.xlsx.

4

DeepL API Settings

Main menu 10.

Where to copy the API key in DeepL

Log in to DeepL.
Open the DeepL account page.
Open the DeepL page for API keys and usage limits.
Select ⧉ next to the API key to copy it.
Paste it into menu 10 in Global Tuber.

API key

ad22********3.fx⧉

10. Register translation DeepL API key

Paste the API key and press Enter ↵ : **********************

This is a DeepL API Developer key.

Your plan is automatically detected from the API key

Enter the usage period start date and press Enter ↵
(Input format: 20261231）: 20260428

Enter the usage period end date and press Enter ↵
(Input format: 20261231）: 20270428

5

YouTube Data API Authentication

Main menu 9. ⇒ YouTube Data API menu 8.

1

Log in with the Google account for the YouTube channel

Log in to Google

xxxxxx@gmail.com

Choose an account

2

If you have multiple channels, select the correct Google account

Choose an account

xxxxxx@gmail.com

Use another account

3

If "This app is not verified by Google" appears

Global Tuber is used by channel owners to manage their own YouTube channels.

If you are using YouTube Data API authentication settings that you created yourself, select Continue.

If you are using an authentication file received from someone else, or you do not recognize its contents, do not continue.

This app is not verified by Google

Continue

Back to safety

4

Select all permissions, then choose Continue

Select the permissions that Global Tuber can access

☑ Select all

☑ Manage YouTube

☑ Manage YouTube videos

☑ Manage YouTube profile

5

Open the email you received and select Review activity

Access has been granted to Global Tuber

xxxxxx@gmail.com

Review activity

After authentication succeeds, config\token.json is created.

Security Notice

DeepL API key config\client_secret.json config\token.json

Keep API keys, authentication files, channel account information, and personal information secure. Do not disclose them to others.

If you use a paid DeepL plan, set usage limits (characters or cost) from the cost control settings in DeepL.

3

Simple Guide

Start with about five languages and a private test video, then get used to the workflow through upload to YouTube.

1

Practice with a private test video of about five minutes

Start with a private test video of about five minutes and repeat the workflow from translation through upload. Use real channel videos only after you are comfortable.

2

Put source files into `Before_translation`

Before_translation Put the source files for translation here.

Title_and_Description.txttitle and description source

Channel_Information.txtchannel information source

Subtitle fileSRT, etc.

Tag for showing subtitles automatically

Open YouTube Studio on a PC, and add yt:cc=on to the Tags field in Upload defaults. For videos that have subtitles, subtitles may be shown by default. The result may vary depending on YouTube specifications and the viewing environment.

YouTube Studio
Settings
Upload defaults
Basic info
Tags
yt:cc=on

3

Check translation targets and translation engines in `Translation-list.xlsx`

１

In the YouTube_Translation sheet of Translation-list.xlsx, use the Translation column to choose whether each language is translated. N copies the source text without translating it, and Y translates it.

２

If the Translation Engine column is blank, the app uses the standard free translation route. SD uses DeepL for especially important short text such as titles and channel names, where translation accuracy matters most (recommended). D uses DeepL for all translations.

4

Practice translating and uploading title + description + subtitles in five languages

Title + descriptionTranslate and adjust as one text file

SubtitlesTranslate and create multilingual subtitles

Check resultCheck and correct the applied content

Using about five languages keeps the results easy to review and lets you practice uploading about four times per day.

5

Keep all language titles within 100 characters

１

Check which languages exceed the 100-character limit and how many characters over the limit they are.

２

Shorten the source title slightly and save it.

３

Press the Enter key to continue. Only the languages that were over the limit are translated again.

Only titles that fit within 100 characters are saved as files for API upload and manual upload.

6

You can also set non-translatable terms

◀❎⛔ @Username ⛔❎▶

Place terms you do not want translated between the one-line non-translation tags shown above. Line breaks make the tag invalid.

Use this for channel names, handles, brand names, product names, proper nouns, and other terms whose meaning would change if translated.

7

Check the output location

For API uploadYouTube_Upload\VIDEO_IDTitle, description, and subtitle files used by YouTube Data API are saved here.

For manual uploadAfter_translationTranslated files for manual upload to YouTube are saved here.

8

Upload with YouTube Data API

Upload title, description, and subtitles together

Use the API files in YouTube_Upload\VIDEO_ID to upload the title, description, and subtitles together.

Reload ( ⟳ ) the subtitle page for the YouTube Studio video and check it.

Practice the translation-to-upload workflow repeatedly with a private test video, and use it on real channel videos only after you are comfortable. Titles, descriptions, and subtitles can be corrected and uploaded again any number of times. However, a channel name can be changed only twice within 14 days.

9

Use the `Placeholder` sheet to insert fixed phrases into subtitles

In the Placeholder sheet of Translation-list.xlsx, register fixed phrases for placeholders such as {WELCOME_WITH_THANKS_1} and {REQUEST_FOR_COMMENTS_1}.

When you write placeholders in subtitles, the app can insert greetings, thanks, comment requests, and other fixed phrases into each language's subtitles. Use this when you want to increase viewer engagement.

Example: Hello everyone around the world. I hope this video can be helpful for you.

4

Task Guide

Use this section to find the right place to check for each task.

Translation

Subtitles

Upload

DeepL

Authentication

Error handling

Source folderBefore_translation

Put the source title, description, channel information, and subtitle files here.

Translated files folderAfter_translation

Translated files for manual upload to YouTube are saved here.

Folder for API uploadYouTube_Upload\VIDEO_ID

Title, description, and subtitle files used by YouTube Data API are saved here.

YouTube Data API folderYouTube_Upload

The channel information file used by YouTube Data API is saved here.

Template folderYouTube_Upload\Templates

Template files for titles, descriptions, and channel information are saved here.

Translate

1

Translate title + description

Translate Title_and_Description.txt and adjust titles in all languages to 100 characters or less.
Adjust text within the character limits in the MAX_LENGTHS sheet of Translation-list.xlsx.
The combined output file is saved in the Title_and_Description_xxxxxx_xxxxxx-★Concatenation.txt format.

2

Translate subtitles

Convert SRT subtitles into YTT or TTML subtitles that can use color bullets, or translate standard SRT, YTT, and TTML subtitles into multiple languages.

YTT subtitles This unofficially supported YouTube subtitle format can express the widest range of styles, including color bullets. This is the recommended format.
TTML subtitles This format can express basic color bullets on YouTube, but the available expression range is limited. It is officially supported by YouTube, but only a small part of the TTML specification can be used.
SRT subtitles This is a standard subtitle format. It cannot use color bullets.

3

Translate title, description, and subtitles together

Use this for continuous translation of title + description and SRT into YTT or TTML subtitles.
Choose this when you want to process subtitles in the same task instead of processing only the title and description.

4

Translate and update channel information

Translate Channel_Information.txt and prepare channel names and descriptions for multiple languages.
Adjust text within the character limits in the MAX_LENGTHS sheet of Translation-list.xlsx.
The combined output file is saved in the Channel_Information_xxxxxx_xxxxxx-(★Concatenation).txt format.
Channel information supports fewer languages than video metadata.

5

Move subtitle blocks and adjust timing

When you run the program, instructions appear on screen. Compare the sample files in the Time_Editing folder before and after execution to understand the result.
Move part of the subtitles and adjust numbering and timestamps.
Follow the manual shown during execution and compare the sample before and after adjustment.
Adjust subtitles in the Time_Editing folder together.

Upload and configure

6

Upload to YouTube

When uploading with the API, use the files in the YouTube_Upload\VIDEO_ID folder. When uploading manually, use the files in the After_translation folder.

7

Set up and check DeepL API

Main menu 10.

Set the API key and usage period so translation can start. If you use a paid plan, set character or cost limits on the cost control page in DeepL.

[Important] Store the DeepL API key securely and never share it.

8

Authenticate with YouTube Data API

Main menu 9. ⇒ YouTube Data API menu 8.

Select the Google account for the YouTube channel, review the Google permissions, and confirm the email. After authentication, check config\token.json.

[Important] The main language (default language) is required for titles and channel names. If it is not set, you cannot upload. You also cannot delete the main language for titles and channel names later.

Store files in the config folder securely and never share them.

Research

9

Three research tools using YouTube API

Main menu 9. ⇒ use the three menus below

5. Multilingual analysis of YouTube keyword search by language: YT_Search.xlsx
6. Detailed channel analysis: YT_channel.xlsx
7. Channel comments and language ratio: YT_Comment.xlsx

When you first run the downloaded sample data, research files are saved in the YouTube_Upload folder.

After that, edit while referring to the downloaded YT_Search.xlsx, YT_channel.xlsx, and YT_Comment.xlsx files.

* Run research on a day when you are not uploading titles, descriptions, or subtitles. Research and upload share a daily limit.

The final Details section explains the technical details. Open only the task you need first.

Check basic setup Translate subtitles Check errors

View FAQ

5

Troubleshooting

Select the symptom to find the likely cause and the steps to fix it.

1. Cannot authenticate YouTube

This can happen during YouTube Data API setup if your email address is not registered as a test user in the OAuth settings after you create the API key. It can also happen if you are logged in with the wrong Google account.

Log in again with the Google account for the YouTube channel, and check the OAuth settings in YouTube Data API if needed.

If an authentication error suddenly appears with a previously authenticated API key, first delete config\token.json and authenticate again. If this does not solve the problem, delete the authentication files in the config folder, obtain a new YouTube Data API key, and authenticate again.

2. Ownership error

This happens when you are not logged in with the Google account for the YouTube channel. Log in again with the correct channel account.

3. Today's quota exceeded

For a new video, you can usually upload titles, descriptions, and subtitles for up to 24 languages per day.

This uses the daily YouTube API quota, so it is best to upload and run research on different days.

Quota calculator (10,000 units per day)

4. No files to upload

If the files have already been uploaded, the target files may have been moved to the Completion folder. Translate again or move the target files back from YouTube_Upload\11-character video ID folder name\Completion.

5. Temporary translation engine error

The translation engine server may be busy. Wait for a while and run the task again. The service endpoint can vary by country and environment, so this may not be something you can fix directly.

6. Research file display is broken

In older versions of Microsoft Excel or Excel-compatible software, thumbnail images and conditional formatting charts may not display correctly. Open the file in a newer Microsoft Excel.

7. Manual YTT / TTML customization error

Manual YTT / TTML edits are outside support if the tag structure is broken. Restore the same structure as the sample, then run the task again.

8. Check the message on screen first

Global Tuber usually shows why it stopped and what to do next. First read the displayed message and check the relevant item.

1Identify the symptomCheck the error message and situation

2Identify the causeCheck common causes

3Solution stepsRun the corrective steps

4Check againCheck whether it works correctly

How to Read Status

Normal: no problem detected

Notice: check the settings or environment

Error: action is required

Do not rely solely on the displayed status. Also check the menu number you selected immediately before and where the file was saved.

If a problem cannot be resolved using this manual and the messages shown by the app, note the situation and contact the email address shown during license authentication or the email address that sent your license key. Include all files in the System\Logs folder.

6

Details

Check what each folder and settings file is used for.

Main Folders and Files

This section summarizes the folders and files that appear repeatedly in the manual. If you are unsure where to look, start with this table.

Name	Role	When to check
Overall workflow	Put source files into `Before_translation`. For manual work, check `After_translation`. For API, check `YouTube_Upload\VIDEO_ID`.	When checking the overall workflow first
`Before_translation`	This folder holds source files before translation. Put title + description, channel information, and subtitle files here before processing.	Before running translation
`After_translation`	Translated files for manual upload to YouTube are saved here.	Before manual upload
`YouTube_Upload\VIDEO_ID`	This placeholder folder name is used in examples for YouTube Data API upload files. Replace it with the actual video ID when checking a real upload folder.	Before API upload
`YouTube_Upload\11-character video ID folder name`	This is the actual per-video upload folder. It contains the title, description, and subtitle files used by YouTube Data API immediately before upload.	Before API upload
`YouTube_Upload\11-character video ID folder name\Completion`	After upload completes, title, description, and subtitle files are saved here. If you upload the same video multiple times, files are not overwritten; they are kept as past backups.	After API upload
`YouTube_Upload`	The channel information file used by YouTube Data API is saved here.	When checking channel information
`YouTube_Upload\Templates`	Template files for titles, descriptions, and channel information are saved here. For channel information, the channel ID and main language (default language) settings are especially important.	When using input templates
`Title_and_Description_xxxxxx_xxxxxx-★Concatenation.txt`	This translated output file combines the title and description. Use it when checking translated titles and descriptions together.	After translating titles and descriptions
`Channel_Information_xxxxxx_xxxxxx-(★Concatenation).txt`	This translated output file combines channel information. Use it when checking multilingual channel names and descriptions.	After channel information translation
`YouTube_Upload\channel_info.json`	This file sets the channel ID and `default_language`. For multilingual global use, `en` is recommended for `default_language`.	During basic setup or when changing channels
`config\client_secret.json`	This is the authentication file downloaded for YouTube Data API. Rename the long downloaded file to this name and place it here.	Before YouTube authentication
`config\token.json`	This file is created after YouTube authentication. It keeps the authentication state. Do not publish it or give it to others.	During YouTube authentication or when authentication errors occur
`System\Logs`	This folder stores error and processing logs. If a problem occurs, check logs from around the time of the problem.	When checking error details
`YTT-Settings.xlsx`	Use this file for YTT subtitle design settings. When checking color bullets and other display options on YouTube, check this file first. YTT and TTML are different formats, so configure them separately when using both. If you edit it manually, back up the original file first and refer to ytt.ytt. Only some items from the reference material are used for YTT settings. Display results may differ by viewing device. Editing `YTT-Settings.xlsx` or YTT subtitle files manually is outside support.	When changing the position or color of YTT subtitles
`TTML-Settings.xlsx`	Use this file for TTML subtitle design settings. Check it when changing subtitle position, color, or display rules. If you edit it manually, back up the original file first and refer to TTML1. On YouTube, only part of TTML1 color and position support is available. Editing `TTML-Settings.xlsx` or TTML subtitle files manually is outside support.	When changing the position or color of TTML subtitles
Non-translation tag	Use a one-line non-translation tag to protect terms that must not be translated. A line break makes it invalid.	When protecting URL, handles, or brand names
Manual customization	When manually editing YTT or TTML, keep the same structure as the sample. If the tag structure is broken, errors can occur. Editing `YTT-Settings.xlsx` or YTT subtitle files is outside support. Editing `TTML-Settings.xlsx` or TTML subtitle files is outside support.	After manually editing subtitles
If the problem is not solved	Contact support only after checking Troubleshooting, FAQ, and Details and the problem is still unresolved. Gather the displayed messages, the tasks you ran, and details of the situation.	Before contacting support
Security notice	Keep API keys, `config\client_secret.json`, `config\token.json`, channel account information, and personal information secure. Do not disclose them to others.	Before sending logs or screenshots

7

FAQ

1

Q

What should I try first?

A

Start with a private test video and repeatedly try the title, description, and subtitles in about five languages. After you are comfortable, move on to channel information and real channel video uploads.

2

Q

Should I use YTT or TTML?

A

In most cases, use YTT because it is easier to edit. Choose TTML only when needed. They are different subtitle formats, so the same settings may not produce exactly the same appearance.

3

Q

Why must titles be 100 characters or less?

A

YouTube titles have a 100-character limit. After you shorten the source title slightly, only languages that exceeded the limit are retranslated. Only titles that fit within 100 characters are saved as files for API upload and manual upload.

4

Q

When should I use non-translation tags?

A

Use them for terms that would cause problems if translated. Examples include @handles, URL, #hashtags, brand names, model names, terms with symbols, and terms whose meaning would change if translated.

5

Q

What is the difference between API upload and manual upload?

A

YouTube_Upload\VIDEO_ID is for API upload. After_translation is for manual upload. The folder to check depends on which method you use.

6

Q

Can I upload multiple times?

A

For private test videos, you can practice repeatedly as many times as needed. However, YouTube Data API has a daily usage limit (quota), so if you reach the limit, run the task again on a later day. Apply the workflow to real channel videos only after you are fully comfortable with it.

7

Q

When should I work on channel information?

A

Work on it after you are comfortable translating and uploading titles, descriptions, and subtitles. Channel information has a wider impact, so first focus on learning the basic workflow with a private test video.

8

Q

Where can I read the detailed technical explanation?

A

Only users who need it should read the final Details section. For normal use, check Simple Guide, Task Guide, Troubleshooting, and FAQ.

Use Global Tuber to translate color-bullet YTT subtitles and upload to YouTube.

Check Before You Start

Supported Environment

What You Need Before You Start

Display Settings

License

Using the app on more than one PC

Free Version and Paid Version

DeepL Character Count

Support Contact

Quick Start

Start Here

Basic Setup

Practice with a Private Test Video

Title, Description, and Subtitle Upload

Details Only When Needed

Complete Basic Setup First

Show File Extensions

Rename client_secret.json

channel_info.json Channel ID and default_language

✔ Recommended methods (either option can work well)

❌ Not recommended (may slow growth)

DeepL API Settings

Where to copy the API key in DeepL

YouTube Data API Authentication

Log in with the Google account for the YouTube channel

If you have multiple channels, select the correct Google account

If "This app is not verified by Google" appears

Select all permissions, then choose Continue

Open the email you received and select Review activity

Security Notice

Simple Guide

Practice with a private test video of about five minutes

Put source files into Before_translation

Check translation targets and translation engines in Translation-list.xlsx

Practice translating and uploading title + description + subtitles in five languages

Keep all language titles within 100 characters

You can also set non-translatable terms

Check the output location

Upload with YouTube Data API

Use the Placeholder sheet to insert fixed phrases into subtitles

Task Guide

Translate

Translate title + description

Translate subtitles

Translate title, description, and subtitles together

Translate and update channel information

Move subtitle blocks and adjust timing

Upload and configure

Upload to YouTube

Set up and check DeepL API

Authenticate with YouTube Data API

Research

Three research tools using YouTube API

Troubleshooting

1. Cannot authenticate YouTube

2. Ownership error

3. Today's quota exceeded

4. No files to upload

5. Temporary translation engine error

6. Research file display is broken

7. Manual YTT / TTML customization error

8. Check the message on screen first

How to Read Status

Details

Main Folders and Files

FAQ

What should I try first?

Should I use YTT or TTML?

Why must titles be 100 characters or less?

When should I use non-translation tags?

What is the difference between API upload and manual upload?

Can I upload multiple times?

When should I work on channel information?

Where can I read the detailed technical explanation?

Rename `client_secret.json`

`channel_info.json` Channel ID and `default_language`

Put source files into `Before_translation`

Check translation targets and translation engines in `Translation-list.xlsx`

Use the `Placeholder` sheet to insert fixed phrases into subtitles