Subtitle Tool & Converter

Quick Start

Convert subtitle files to other file formats or use the tool to check subtitles for guidelines, repair or correct them.

Endpoint

This endpoint is used to convert subtitle files.

POST https://api.editingtools.io/v2/subtitles

Authentication

This API requires Basic Authentication. The "Authorization" header should be set with the Base64 encoded string of "apikey:YOUR_API_KEY".

Authorization: Basic <base64Encoded(apikey:YOUR_API_KEY)>

Headers

Request Body

The request can contain the following parameters:

There are more options to choose, please contact our free support for more details how to use them.

cURL Examples

The following examples show how to use the API with cURL commands. If you are using a different language, we recommend using https://curlconverter.com to convert the commands for other languages like: PHP, JavaScript, Python, Ruby, Rust, Ansible, C , C#, ColdFusion, Clojure, Dart, Elixir, Go, HAR, HTTP, HTTPie, Java, JSON, Kotlin, MATLAB, Node.js, Objective-C, OCaml, PowerShell, R, Swift and more.

cURL Request Example 1

This is an example of how to convert a subtitle file (SRT to CSV).

curl -X POST https://api.editingtools.io/v2/subtitles \
-u "apikey:YOUR_API_KEY" \
-F file=@/path/to/subtitle.srt \
-F source=srt \
-F format=csv \
-F framerate=25 \
-F removeEmpty=true \
-F mergeIdentical=true \
-F removeSuperfluousSpaces=true \
-F fixInvalidTags=true \
-F removeDurationZero=true \
-F fixOverlapping=true

cURL Request Example 2

This is an example of how to convert a subtitle file and return the output as a Base64 string.

curl -X POST https://api.editingtools.io/v2/subtitles \
-u "apikey:YOUR_API_KEY" \
-F file=@/path/to/subtitle.srt \
-F source=srt \
-F format=csv \
-F framerate=25 \
-F removeEmpty=true \
-F mergeIdentical=true \
-F removeSuperfluousSpaces=true \
-F fixInvalidTags=true \
-F removeDurationZero=true \
-F fixOverlapping=true \
-F base64=true

Responses

Success (HTTP 200 OK)

If the file was successfully converted, the API will return a 200 OK status code with a JSON object containing the file details.

Response Example 1

The request returns the path to the file.

{
    "code": 200,
    "status": "Success",
    "timestamp": "2025-05-22T19:29:27Z",
    "data": {
        "fileName": "mysubtitle.csv",
        "fileUrl": "https://editingtools.io/path/to/file/mysubtitle.csv",
        "fileSize": 1504,
        "fileChecksum": "3e85da48d39823444424aba2f41a57db"
    }
}

Response Example 2

The request returns the file as Base64 string.

 {
    "code": 200,
    "status": "Success",
    "timestamp": "2025-05-22T19:29:27Z",
    "data": {
        "fileName": "mysubtitle.csv",
        "fileBase64": "Tm8sVGltZWNvZGUgSW4sVGltZW...jE3OjIzIiwiMDA6MDA6MTMsM",
        "fileSize": 1504,
        "fileChecksum": "3e85da48d39823444424aba2f41a57db"
    }
}

Error Responses

Error responses typically include an appropriate HTTP status code and a JSON body containing an error message.

{
    "code": "400",
    "status": "Bad Request",
    "timestamp": "2025-05-22T19:29:27Z"
}

Download File

After the process is successfully completed, the file can be downloaded using the values returned under fileUrl and fileName. The generated file will be online for a maximum of 20 minutes. After download, you can validate the file with the MD5 hash provided in fileChecksum.

cURL Request Example (macOS or Linux)

Example to download the file to the Desktop. Uses -o to specify the output file path.

curl -o ~/Desktop/{fileName} "{fileUrl}"
	                        
curl -o ~/Desktop/mysubtitle.csv "https://editingtools.io/path/to/file/mysubtitle.csv"

cURL Request Example (Windows with PowerShell)

curl -o "$env:USERPROFILE\Desktop\{fileName}" "{fileUrl}"
	                        
curl -o "$env:USERPROFILE\Desktop\mysubtitle.csv" "https://editingtools.io/path/to/file/mysubtitle.csv"

cURL Request Example (Windows Command Prompt with cURL installed)

curl -o "%USERPROFILE%\Desktop\{fileName}" "{fileUrl}"
	                        
curl -o "%USERPROFILE%\Desktop\mysubtitle.csv" "https://editingtools.io/path/to/file/mysubtitle.csv"

Python3 Request Example

import os
import urllib.request

name = "mysubtitle.csv"
url = "https://editingtools.io/path/to/file/mysubtitle.csv"

# Construct the path to the Desktop for example
local_path = os.path.join(os.path.expanduser("~"), "Desktop", name)

# Download the file
try:
    urllib.request.urlretrieve(url, local_path)
    print(f"File downloaded successfully and saved to: {local_path}")
except Exception as e:
    print(f"Failed to download file: {e}")

wget Request Example (macOS or Linux)

Example to download the file to the Desktop. Uses -O to specify the output file path.

wget -O ~/Desktop/{fileName} "{fileUrl}"

wget -O ~/Desktop/mysubtitle.csv "https://editingtools.io/path/to/file/mysubtitle.csv"

wget Request Example (Windows with PowerShell)

wget -O "$env:USERPROFILE\Desktop\{fileName}" "{fileUrl}"

wget -O "$env:USERPROFILE\Desktop\mysubtitle.csv" "https://editingtools.io/path/to/file/mysubtitle.csv"

wget Request Example (Windows Command Prompt with wget installed)

wget -O "%USERPROFILE%\Desktop\{fileName}" "{fileUrl}"

wget -O "%USERPROFILE%\Desktop\mysubtitle.csv" "https://editingtools.io/path/to/file/mysubtitle.csv"

Endpoint URL

Endpoint URL to convert subtitle files.

https://api.editingtools.io/v2/subtitles

Authentication

This API requires Basic Authentication. The "Authorization" header should be set with the Base64 encoded string of "apikey:YOUR_API_KEY".

Authorization: Basic <base64Encoded(apikey:YOUR_API_KEY)>

Data Handling

Request parameters must be UTF-8 encoded. Results are returned as UTF-8-encoded JSON. By default, datasets will be inside the data tag.

Error Handling

This API service uses standard HTTP response codes to indicate whether a method was completed successfully. HTTP response codes in the 2XX range indicate success. Responses in the 4XX range indicate some sort of failure, while responses in the 5XX range indicate an internal system error that cannot be resolved by the user. The following error codes are used by the API:

Rate Limits

To prevent abuse and spam, the API has limits at various levels. If you receive error code 429 (Too Many Requests), it means you have reached a rate limit.

If you receive a rate limit error, you should stop making requests temporarily. If the retry-after response header is present, you should not retry your request until after that many seconds has elapsed. To prevent rate-errors, we recommend to wait 300 ms to 800 ms between requests to the same endpoint.

Also there is a general limit to the api and all requests made:

The general limits per minute and per hour can be changed upon request.

Upload Limits

The maximum upload size for any single request — including file uploads — is 100 MB. This is a hard limit and applies regardless of your API plan or usage level.

If your request exceeds this size, it will be rejected before reaching our servers. To ensure successful uploads:

• Make sure uploaded files are under 100 MB.
• For larger media, consider splitting files before upload.
• Requests close to the limit may still fail due to encoding or header overhead.

Timezone

This API endpoint returns the time as an ISO 8601 timestamp in the UTC time zone. These timestamps look like 2025-01-10T15:05:06Z.

Localization and Languages

This API supports multiple languages. For instance, it can display the text of a status message in a different language.

Accept-Language: LANGUAGE

Example

To set the preferred response language to Spanish, add this header:

Accept-Language: es

cURL Example

To apply the language in a cURL request, add the following header:

-H "Accept-Language: es"

Available Languages

The following list contains all the currently available languages. Note that setting a language header does not guarantee a translated response, as not all texts are translated. If no language is set or a translation is unavailable, the default response will be in English.