In addition to syncing resource files through repository integrations or file uploads, you can create new segments directly inside the Editor, either manually or by uploading a CSV file.
How to create segments
Go to the Editor
Select project, container, & input method
Select the target Project from the dropdown menu.
Select the resource file Container to which the segments belong.
Choose your creation method:
Click Next.
Configure segment fields
In the segment creation grid, configure your segment data (if you uploaded a CSV file, these fields populate automatically):
Key: Enter a unique identifier for the segment.
Source text: Type the source content in the primary language column (e.g., English).
Labels: Click the + icon under Labels to assign existing labels or type to create new ones.
Status: Set the segment status to Draft or Approved via the dropdown menu.
Plural rules & row actions: Click the three-dot menu under Actions to toggle Plural settings or click Remove segment to discard a row.
(Only for manual entry) Click + Add segment at the bottom left to add additional rows manually.
Finalize creation
Review the total segment count displayed at the bottom right (e.g., Total segments created: 100/100).
Click Create segments.
Your newly created segments appear instantly inside the Editor list view.
CSV file requirements for segment imports
To import segments via a CSV file, ensure your file adheres to the following guidelines:
File limits: Maximum 100 segments per upload and 5MB total file size. Any segments beyond the 100-entry limit are automatically rejected.
Headers: Your CSV file must contain the following column headers:
segmentKey(Required): The unique key identifier for the segment.sourceContent(Optional): The text content of the source segment. Leaving this blank creates an empty segment.groupKey(Optional): Used for formats with hierarchical group keys (e.g., Gettext PO, Qt Linguist TS, Standard INI, or Twine TXT).plural(Optional): Set toTRUEorFALSE(defaults toFALSE).status(Optional): Set todraftorapproved(defaults to project settings if omitted).labels(Optional): Comma-separated list of labels (e.g.,"red label, blue label, new").
💬 Please note: For nested formats like YAML, JSON, or XLIFF, use dot notation in the segmentKey column to define hierarchy (e.g., menu.button.title). If a key name contains a literal dot, enclose that segment in quotation marks to prevent unwanted splitting.
Need more help?
Couldn't find what you were looking for? Reach out to our team at [email protected], and we will gladly assist you.











