This guide will help you set up your first project in PTC and make your software or app multilingual using our AI-powered translation platform.
Sign up for PTC
To begin using PTC:
Sign up for a free trial or purchase a subscription.
Check your email for login details.
Log in to your account.
Choose How You Want to Use PTC
Once logged in, you’ll launch the project setup wizard. This wizard helps you decide how to translate your resource files.
You have three options:
Integrate PTC with your Git repository
Use this option for automated, continuous localization. PTC monitors your GitHub, GitLab, or Bitbucket repository, translates updated content, and sends the translations back via merge requests.
What PTC needs:
- Read access to monitor your resource files for changes
- Write access to create merge requests with completed translations
Upload resource files manually
Uploading resource files to PTC is a great way to evaluate PTC’s translation quality. You’ll manually upload your resource files to PTC and receive a ZIP file with the translations. You can also view and fine-tune translations from the PTC dashboard.
Use the PTC API
Best for teams who want full CI control without granting access to their code repository.
With the API, you can:
- Upload resource files programmatically
- Associate them with a specific branch
- Receive a callback when translations are ready
- Download completed translations
Provide Project Details and Select Languages
Software often includes small, out-of-context text strings, like button labels, tooltips, or error messages.
PTC uses your input to generate better translations, especially for these types of short or ambiguous UI strings.
You’ll answer a few questions:
- What’s the name of your product?
- What does it do?
- Who is your target audience?
Next, select your target languages and decide how PTC should handle common terms like “email” — whether to keep them in English or translate them.
This context helps PTC deliver Better Than Human Translations that sound natural, accurate, and on-brand.
Add Your Resource Files
Now it’s time to provide the resource files you want PTC to translate.
Git Integration
PTC will automatically scan your connected repository and detect supported resource files. You’ll be asked to:
- Confirm which files to translate
- Choose to include/exclude specific files or languages
- Define output paths for the translated versions
Manual File Upload
Drag and drop or browse to select files and specify output paths for translated files.
Depending on your project, you may store these strings in one or more file formats. PTC supports various resource file formats, including:
Gettext.po
JSON
YAML
Adobe Commerce / Magento .csv
Android
Apple .strings
Apple .stringsdict
Apple .plist
Java Properties
JSON Array
Choose Whether You Want to Use Existing Translations
PTC delivers the best results when it can translate from scratch and use your project’s context. Still, if you have existing translations, PTC can use them:
Git Integration
PTC auto-detects existing translation files in your repository. You can choose to:
- Use or ignore all translations
- Use or ignore translations by language
- Use or ignore individual files
Manual Upload / API
You can include existing translation files during upload or via the API.
Receive Your AI Translations
Once setup is complete, PTC’s AI will translate your content. How you receive the translations depends on your integration method:
Git Integration
Translations are delivered to your repository as a merge request. You can review and merge them when ready.
Manual File Upload
Download a ZIP file with your translations or manage translations from the Translations tab in your PTC dashboard
If you choose API integration, you’ll receive your API token during setup. From there, you’ll send resource files via API and receive a callback when translations are ready.
