Skip to main content

Create a Single String

Add individual string resources to your application:
1

Navigate to Strings

Go to Strings page (/strings) from the sidebar
2

Select Application

Choose an application from the dropdown at the top
3

Click New String

Click the New String button
4

Fill in Form

Complete the string details:
  • String Key (required, max 100 characters) - Unique identifier
  • Language - Select from dropdown
  • String Value (required) - The actual text
  • Description (optional) - Context or usage notes
5

Create

Click Create String Resource to save
Use consistent key naming like screen.action.element (e.g., home.button.welcome)

Bulk Upload Strings

Upload hundreds or thousands of strings at once using CSV, XML, or JSON files.

Prerequisites

Application created
CSV, XML, or JSON file prepared with string data
File follows the correct format (see below)

File Formats

  • CSV Format
  • JSON Format
  • XML Format
key,value,languageCode,description
welcome_message,Welcome!,en,Greeting message
goodbye_message,Goodbye!,en,Farewell message
app_title,My Application,en,Main app title

Upload Steps

1

Navigate and Select

  • Go to Strings page
  • Select your application
2

Click Bulk Upload

Click the Bulk Upload button in the header
3

Choose File

Select your CSV, XML, or JSON file
4

Review Preview

  • Review the data preview
  • Check for validation errors
  • Resolve any duplicate conflicts
5

Upload

Click Upload to complete the import

Bulk Upload Features

S3 Integration

Cloud-native file processing for large uploads

Real-time Progress

WebSocket-powered progress tracking

Duplicate Resolution

Bulk resolution system for key conflicts

Auto Conversion

Automatic CSV/XML/JSON format conversion

Resume Capability

Recover from upload interruptions

Error Resolution

Fix validation errors before final upload

View and Filter Strings

Find strings quickly using powerful filtering options:

Filter Options

Select All Applications or filter by specific app
Filter strings by language code (en, es, fr, etc.)
Search by string key or value using the search box
Switch between tabs:
  • All Strings - Complete list
  • Recently Modified - Last 7 days

Edit a String

Modify existing string values or descriptions:
1

Find String

Navigate to Strings and locate the string in the table
2

Click Edit

Click the Edit icon (pencil) for the string
3

Modify

Update:
  • String value
  • Description
4

Save

Click Save Changes
You cannot edit the string key or language after creation. Create a new string if you need to change these.

Delete Strings

Remove strings you no longer need:
  • Single Delete
  • Bulk Delete
1

Find String

Locate the string in the table
2

Click Delete

Click the delete icon (trash)
3

Confirm

Confirm deletion in the dialog

Export Strings

Download your strings for backup or external use:
1

Navigate to Strings

Go to the Strings page
2

Apply Filters

(Optional) Apply filters to export specific strings
3

Click Export

Click the Export button
4

Choose Format

Select CSV or JSON format
5

Download

Download begins automatically

Best Practices

Consistent Keys

Use naming conventions:
  • screen.action.element
  • module_feature_component
  • camelCase or snake_case

Add Descriptions

Document complex strings with:
  • Usage context
  • Placeholder meanings
  • Special formatting notes

Use Bulk Upload

For large datasets:
  • Faster than manual entry
  • Reduces errors
  • Easy to review in spreadsheet

Regular Exports

Export strings regularly:
  • Backup your data
  • Share with translators
  • Version control

Troubleshooting

Possible causes:
  • Application not selected
  • Language doesn’t exist in app
  • String key already exists
  • Required fields missing
Solution: Verify all requirements and use unique keys
Possible causes:
  • File format doesn’t match template
  • Duplicate keys present
  • Language codes don’t exist
  • Validation errors in data
Solution: Review preview errors and fix before uploading
Check:
  • Correct application selected
  • String language matches SDK language
  • API token has correct permissions
  • SDK cache has been refreshed

Next Steps