
Designed for creators. Free to use. Ready to scale.
Built by subtitlers. Powered by freedom!
Creating a subtitle project may look like a simple first step. You open the subtitle editor, load the video, import the template and start working.
But in professional subtitling and media localization, project creation is much more than a technical formality.
It is the foundation of the entire subtitle workflow.
Every decision made at the beginning of a project can affect timing accuracy, QC results, export compatibility and the overall speed of work. A wrong FPS, an incorrect template format, an unclear timing base or a mismatched ruleset may not create an obvious problem immediately. But those issues often appear later - during editing, export, review or advanced quality control.
That is why Sublandia Editor treats project creation as an important part of the subtitling process.
A well-created project helps reduce errors, prevent unnecessary rework and make the entire subtitle workflow more stable, predictable and efficient.
Subtitle editing is cumulative.
Every timing adjustment, every subtitle split, every reading speed decision and every export result depends on the technical setup of the project.
If the project is created incorrectly, the mistake does not stay isolated. It can affect the whole file.
For example, if the wrong FPS is selected, the timing may look acceptable during editing but become inaccurate when exported to a frame-based format. If the wrong subtitle format is selected for the template, the imported file may not behave as expected. If the ruleset does not match the client or platform requirements, QC problems may appear late in the workflow.
In other words, many subtitle errors are not created while editing. They begin before editing starts.
The purpose of this guide is to help you understand each step of project creation in Sublandia Editor and why it matters.
Before creating a new project in Sublandia Editor, you should first understand the technical and delivery requirements of the job.
This includes checking:
This step is important because the final delivery requirements should guide the setup from the beginning.
If you only think about export at the end of the project, you may discover too late that the subtitle file was edited under the wrong assumptions.
A professional subtitle workflow should always begin with the final delivery in mind.
Different subtitle formats and platforms may have different technical expectations.
An SRT file may be suitable for one workflow, while a TTML file may be required for another. Some delivery workflows are time-based, while others may require stricter frame-aware formatting. Some clients may use custom rulesets for character limits, reading speed, minimum duration, shot changes or subtitle positioning.
If the wrong ruleset or export target is selected too late, the project may need additional correction before delivery.
By checking the project requirements first, you reduce the risk of late-stage QC problems and export errors.
The next step is to check the video file before importing it into Sublandia Editor.
At this stage, you should confirm:
For now, Sublandia Editor accepts MP4 video files. That means the video material should be prepared in MP4 format before creating the project.
A video offset can cause subtitles to appear too early or too late.
Even if the subtitle template is technically correct, it may not match the video if the video has a different start point, intro, black frames, countdown, broadcaster slate or platform-specific versioning.
If an offset exists, it is better to identify it before editing begins.
Sublandia Editor allows you to adjust the offset during project setup when needed. This helps align the subtitle timing with the actual video material from the beginning.
FPS is one of the most important technical values in subtitle work.
If the FPS of the project does not match the FPS required for the video or export, timing problems can appear later. This is especially important when working with frame-based subtitle formats or strict delivery requirements.
Sublandia Editor can recognize the FPS of the loaded video, but the user should still check whether the detected FPS matches the project requirements.
The detected FPS should not be accepted blindly if the client specification requires a different delivery base.
Before loading a subtitle template into Sublandia Editor, it is a good practice to open it in a text editor and check whether the file is properly formatted.
This is especially important when working with templates received from clients, agencies, previous tools or older subtitle workflows.
You should check:
A subtitle template may look correct at first glance, but small formatting issues can create import problems or later QC errors.
For example, an SRT file with broken numbering, invalid timecode separators or inconsistent line breaks may not import as expected. A TTML file may contain structure, styling or timing information that needs to match the intended workflow.
If you have information about the FPS or timing base of the template, compare it with the video and project requirements before importing it.
This helps prevent timing mismatches and reduces the need for manual correction later.
After checking the project requirements, video file and subtitle template, you can open Sublandia Editor and create a new project.
This is where the technical foundation of the project is defined.
During project creation, you should carefully complete each setup step.
Start by giving the project a clear and recognizable name.
A good project name helps you identify the job later, especially when working on multiple subtitle projects, multiple languages or different versions of the same video.
A useful project name may include:
For example:
Documentary_Ep01_Serbian_TTML_ClientVersion
A clear naming structure helps reduce confusion, especially in localization workflows with multiple files and deliverables.
Next, load the video file into Sublandia Editor.
After loading the video, check which FPS the editor has recognized.
Do not skip this step.
The detected FPS should be compared with the information you already have from the project specification, video metadata or client instructions.
If the project requires a specific FPS for export, make sure the setup supports that requirement.
If the video does not match the subtitle template, check whether an offset needs to be applied.
Offset issues often happen when the video file contains additional material at the beginning, such as:
If the template starts at a different point than the video, the subtitles will not align correctly.
Adjusting the offset during project creation helps ensure that timing work starts from the correct position.
When importing a subtitle template, select the format that matches the actual file.
For example, if your template is an SRT file, select SRT. If your template is a TTML file, select the correct TTML-related option when available.
Choosing the wrong template format can lead to incorrect import behavior, missing information or timing issues.
This step is especially important when working with professional subtitle templates that may contain format-specific timing, styling or structural information.
The template format should always match the file you are importing, not just the format you plan to export later.
Sublandia Editor supports different timing approaches depending on the needs of the project.
The timing mode affects how subtitle start and end times are handled internally and during export.
Strict timing mode uses continuous internal time. Frame rounding is applied only when needed for frame-based formatting or export.
This mode is useful when you want to preserve flexible internal timing while still supporting frame-based output requirements.
It helps keep editing smooth while allowing the export process to respect frame-based formatting when necessary.
Precise timing mode snaps all start and end values to exact frame boundaries.
This mode is useful when the project requires strict frame accuracy throughout the editing process.
It can be especially relevant for workflows where every subtitle timing point must align directly to the frame grid.
Timing mode is not just a technical preference.
It affects how the project behaves during editing and export.
Choosing the wrong timing mode can create confusion between what the editor shows, how the subtitles behave and what the final exported file contains.
That is why the timing mode should be selected according to the delivery requirements of the project.
A ruleset defines the quality and formatting expectations for the subtitle project.
Depending on the project, a ruleset may include rules for:
Selecting the correct ruleset at project creation helps Sublandia Editor apply the right quality logic from the beginning.
If the ruleset needs adjustment, configure it before importing or editing the template whenever possible.
Rulesets are not only useful for final QC.
They are part of the working environment.
If you apply the correct ruleset from the beginning, you can work with the project requirements in mind while editing. This reduces the risk of discovering too many issues only after the subtitle file is already finished.
In professional localization, this can save a significant amount of time.
After the project name, video, FPS, offset, template format, timing mode and ruleset are set, load the subtitle template.
At this point, the project has a much stronger technical foundation.
You are no longer importing the template into an undefined environment. You are importing it into a project that already knows what kind of workflow, timing behavior and quality expectations it should follow.
This is the correct moment to begin actual subtitle editing.
Every skipped or incorrect setup step can create problems later.
Some errors appear immediately. Others stay hidden until export or advanced QC.
Common late-stage problems include:
These problems are often more difficult to fix after editing is complete.
A small setup mistake at the beginning can become a large correction task at the end.
This is why project creation should be treated as part of subtitle quality control, not as a separate administrative step.
Speed in subtitling is not only about editing faster.
It is also about avoiding unnecessary rework.
When the project is created correctly, the editor can focus on the actual work:
The workflow becomes more fluid because fewer hidden technical issues interrupt the process.
This is especially important when working on multiple subtitle projects. A clean setup can save time on one project, but the real benefit becomes much larger across many projects, languages and deliverables.
Better project creation leads to:
In professional subtitling, small improvements in workflow stability can have a major impact on productivity.
Sublandia Editor approach: correctness starts early
Sublandia Editor is designed around the idea that subtitle quality starts before editing.
The project creation system helps users define the most important technical and workflow settings early:
This approach helps prevent error accumulation.
Instead of waiting until export to discover that something is wrong, Sublandia Editor encourages users to build a reliable project foundation from the start.
That makes subtitle editing more consistent, more transparent and easier to control.
For translators, subtitle editors, QC specialists and localization teams, this means less time spent fixing avoidable mistakes and more time spent improving the actual subtitle quality.
Before you start editing, check the following:
This checklist helps reduce mistakes and improves the stability of the entire subtitle workflow.
FAQ
Project creation defines the technical foundation of the subtitle workflow. FPS, timing mode, ruleset, template format and video offset can all affect editing, QC and export. If these settings are wrong, problems may appear later and require additional correction.
Before creating a subtitle project, check the project ruleset, final export format, required FPS, video format, video offset, template format and template structure. These details help ensure that the project starts correctly.
FPS affects how time is interpreted in frame-based workflows. If the FPS is wrong, subtitle timing may become inaccurate, especially during export or when working with formats that require frame-aware timing.
Sublandia Editor currently supports MP4 video files. Before creating a project, make sure your video material is available in MP4 format.
A subtitle ruleset defines the technical and editorial requirements for a project. It can include limits for reading speed, characters per line, subtitle duration, gaps, line count, timing behavior and other QC rules.
The ruleset should be selected as early as possible, ideally during project creation. This allows you to edit according to the correct requirements from the beginning instead of discovering problems at the end.
Strict timing mode uses continuous internal time and applies frame rounding only when needed for frame-based formatting or export. Precise timing mode snaps all subtitle start and end values to exact frame boundaries.
Precise timing mode is useful when the project requires all subtitle timing points to align exactly with frame boundaries. This may be important for strict frame-based workflows or specific delivery requirements.
Strict timing mode is useful when you want smoother continuous internal timing while still allowing frame rounding for frame-based formatting or export. It can be a good option for workflows that do not require every edit point to be snapped immediately to the frame grid.
Checking the template in a text editor helps you identify formatting problems, broken timecodes, encoding issues or file structure problems before importing it into the subtitle editor.
Yes. Wrong FPS, incorrect template format, mismatched timing mode or the wrong ruleset can create export issues or QC problems. Some of these errors may only become visible at the final delivery stage.
Sublandia Editor helps users define important project settings early, including video file, FPS, offset, template format, timing mode and ruleset. This helps create a more reliable workflow and reduces the risk of error accumulation.
Something on your mind?
Contact us