PTC

Translate CSV Files Online with AI

Translate CSV files into 40+ languages with AI. PTC (Private Translation Cloud) learns your product's vocabulary and visually reviews the rendered catalog or app, so you ship without manual QA per language.

Drop in a .csv file from any structured export. Product catalog, app resource strings, dataset. PTC returns column-clean translations in minutes.

E-commerce teams running Shopify, WooCommerce, or Magento use PTC for product catalogs. App teams use it for key,source string exports. Data teams use it for dataset translation at scale.

Start your free 30-day trial - translate your CSV right now

  • 20,000 words into 2 languages, free
  • 40+ languages supported
  • Visual translation review of the rendered catalog or app included
  • ISO 27001 certified - security and compliance off your list
  • No credit card required

Start free trial

Translate your CSV file in 3 steps

  1. Start a project in your PTC dashboard. Choose your source language. PTC uses the source to pick the right translation engine. It also skips strings that do not need translating, such as URLs, brand names, and identifier columns.
  2. Upload your .csv file. PTC supports UTF-8 encoded files with a key column and one or more content columns. That covers most CSV localization workflows in apps, SaaS products, and e-commerce platforms. Drag and drop or browse; the word count shows instantly.
  3. Pick target languages and confirm. PTC translates in the background. Review individual strings in the Translations tab, then download a ZIP with one translated CSV per language. Each file keeps the same structure as your source - ready to import.

The free trial covers 20,000 words into 2 languages with no credit card. That is enough to translate a typical Shopify product catalog or app string export end-to-end before you decide whether to subscribe.

What sets PTC apart for CSV translation

Each item below links to the detailed section further down the page.

PTC learns your product's vocabulary and brand voice

PTC analyses your source file on upload. It automatically generates a product description and uses that description to translate with the right tone and terminology.

If your product calls a record a "Order" rather than a "Purchase", PTC keeps that distinction across every target language. The same description carries over to every future update to the same project. You can review and edit the auto-generated description before translation runs.

This is why context matters. Most tools see a CSV value like "Run" and translate it without knowing whether the user means "execute a scan" or "go for a run". PTC learns your terminology and audience first. 99.5% of translations go live without any edits.

Visual translation review of your rendered catalog or app - ship without manual QA per language

PTC does not stop at the translated CSV. Visual translation review sees PTC's own translations rendered inside your actual storefront, app, or dashboard. It catches issues that no string-level review can see:

  • A German product title that overflows a Shopify card layout.
  • A French description that sits awkwardly inside a WooCommerce product page.
  • A long Spanish address that breaks a fixed-width column in a printed invoice.

For storefronts and dashboards that render in a browser (Shopify, WooCommerce, Magento, custom admin UIs), the right flavor is the browser extension. Install it once. Record a short walkthrough of your top product pages or screens. PTC replays the recording after every translation update.

For native apps that consume the CSV but do not render in a browser, the screenshot upload flavor applies. Upload one screenshot per language per screen. PTC inspects the rendered result the same way.

PTC fixes what it controls. Issues in the CSV (the verb-noun mismatch, the overflowing title) get fixed automatically. PTC picks a shorter synonym, restructures the sentence, or flags rows that need manual attention. Issues that live in your source code or theme template come back as ready-to-paste prompts for Cursor or Claude Code. Your dev team applies the fix in seconds.

You do not ship a translated CSV and hope. You ship a verified, multilingual catalog or app.

Glossary and translation memory per project

Add a glossary entry once. For example: "Cart = Carrito" for Spanish. PTC applies the entry across every CSV in the same project, now and on every future update. You never re-upload TMX files between runs.

You can manage glossary entries in two ways. The PTC dashboard provides an editor for ad-hoc entries. The PTC REST API supports glossary import and export for teams that maintain terminology in a separate system.

Column-perfect output: columns, keys, and quoting preserved

PTC never renames, drops, or merges columns. Delimiters, column order, identifier columns, and CSV quoting come back exactly as they went in.

Identifier columns (SKU, key, ID, handle, image URL, price) are detected and left untouched. PTC does not translate product-blue-shirt-large. PTC reads and writes UTF-8 CSV with proper BOM handling. Translated content displays correctly across accented characters and non-Latin scripts like Arabic, Japanese, and Chinese. No é corruption on the way out.

If your CSV is key,en,fr,de,es,it (one column per language), PTC fills the empty target-language columns from the source column. If your CSV is key,source and one file per language, PTC generates one output .csv per target language. For the canonical guide on preparing a CSV that translates cleanly (keys, placeholders, plurals, special characters, UTF-8 encoding), see how to prepare a CSV file for translation.

Placeholders, HTML, and plurals all handled correctly

PTC recognises every common placeholder convention. That includes %s, %1$d, %(name)s, {count}, and {{name}}. PTC keeps each placeholder in the right position for every target language. It never translates the placeholder itself.

PTC parses HTML inside CSV cells. For Shopify Body (HTML) columns, PTC translates only the text content and preserves every tag, attribute, and inline placeholder. Standard CSV escaping (RFC 4180) is respected on the way out. Double quotes, embedded commas, embedded newlines.

For plurals, PTC reads the conventional .zero / .one / .other suffix pattern and generates the right number of plural forms per target language. Japanese needs 1 form. English needs 2. Polish needs 3. Arabic needs 6.

PTC translates Shopify, WooCommerce, and Magento product exports

E-commerce CSVs are the hardest kind to translate. The translated string ships straight into a store layout that is unforgiving about length. A German product title that is accurate but 30% longer than the English original will wrap, truncate, or break the grid. PTC handles three flavors of e-commerce CSV with care:

Shopify product exports. PTC reads the Shopify CSV schema and translates Title, Body (HTML), Vendor, Option1 Value, Image Alt Text, and tag fields. SKU, handle, price, and inventory columns are left untouched. The output .csv is ready for re-import via Shopify's bulk product editor.

WooCommerce and Magento product exports. Same pattern. PTC translates the human-readable columns (product name, short description, long description, attribute values) and leaves identifiers, prices, and stock status alone.

App string catalogs. If your CSV is key,en,fr,de,es,it, PTC fills the empty target-language columns. If your CSV is key,source and one file per language, PTC generates one output .csv per target language.

For content that lives outside your CSV (app store listings, help center articles, onboarding emails), PTC's Paste to Translate feature uses the same project context. Terminology stays consistent across everything you ship.

Automate CSV translation from your Git repository or CI pipeline

PTC integrates with GitHub, GitLab, and Bitbucket. New strings in your .csv file trigger an automatic translation run. The resulting translated files come back as a pull request. Review and merge when you are ready.

For CI/CD-driven workflows, the PTC API reference covers the REST endpoints for uploading a CSV, polling for completion, and downloading translated files. Large CSVs can be sent through the API for automated, batched translation at scale.

Translate more than CSV

PTC also handles .po, .pot, .json, .yml, .xml, .strings, .xcstrings, .properties, .resx, .arb, and many more. A mixed-format project translates under one project and one glossary.

Translate product launches, email campaigns, and store-listing copy

Marketing copy for product launches, email campaigns about catalog updates, and store-listing descriptions all live outside the CSV. PTC's Paste to Translate handles that copy in the same project. Paste the source text, choose target languages, get back translations that use the same glossary and brand voice as your catalog.

Translate bulk catalog imports and supplier content with the PTC API

Bulk catalog imports that need translation as data arrives, and supplier-provided product descriptions in their source language, can flow through the PTC API. The PTC REST API translates this content on demand with Bearer-token authentication, using the same glossary and brand voice as your CSV translations.

Pricing: 30-day free trial, then Pay-As-You-Go

The free trial covers 20,000 words into 2 languages with no credit card. When the trial ends, PTC offers Pay-As-You-Go. No subscription. No minimum commitment. The first 500 words every month are free, and you only pay for the rest. The pricing page has a cost calculator. Sign up with a company email for an extended business trial.

PTC is ISO 27001 certified

PTC handles your data and your users' data to internationally recognized security standards. Your security and compliance team can sign off without extra review.

CSV localization essentials, explained

CSV is a portable format built for localization

CSV (Comma-Separated Values) is a plain text format that stores data in rows and columns. It is widely used for localization because it is simple, portable, and easy to work with across tools, frameworks, and e-commerce platforms.

From upload to a ready-to-import ZIP

Upload your CSV file and add a short description of your product. PTC uses that context to generate accurate translations into your chosen languages. Once translation is done, head to the Translations tab to review individual strings, then download your translated files as a ZIP from the Resource files tab. For a full overview, see the getting started guide.

PTC supports UTF-8 files with key and content columns

PTC supports UTF-8 encoded CSV files with a key column and one or more content columns. That covers most CSV localization workflows used in apps, SaaS products, and e-commerce systems like Shopify or Magento.

Built for Shopify, Magento, and bulk store catalogs

PTC works well for Shopify, Magento, and similar platforms. You can translate product titles, descriptions, and other strings in bulk, with the same context-aware AI that keeps terminology consistent across your store.
PTC also includes Paste to Translate for content that does not live in your CSV, like app store listings, help center articles, onboarding emails, and support content. Since it uses the same project context, terminology stays consistent across everything you ship.

Your delimiters and structure stay intact

PTC keeps your original CSV structure intact, including delimiters, column order, placeholders, and formatting, so your translated file is ready to import.

UTF-8 keeps every script and accent correct

PTC supports UTF-8 encoded CSV files, which allows translated content to display correctly across accented characters and non-Latin scripts like Arabic, Japanese, and Chinese.

Large CSV files translate at scale

Large files can be uploaded in the app or sent through the API for automated translation at scale.

Ready to ship a verified catalog?

Upload your .csv file. PTC translates it into 40+ languages and visually reviews the rendered catalog or app in every one. You ship with confidence.

Start your free 30-day trial - 20,000 words on us, no credit card required.

For a deeper take on what makes a CSV translation-ready, see how to prepare a CSV file for translation. For broader software localization patterns, see AI software localization built for CI/CD pipelines.