String Catalog Logo
String Catalog
Home
Docs
Manual Upload Projects

// Getting Started

Manual Upload Projects

Localize iOS xcstrings files without connecting a repository. Upload your file, run translation, and download localized output — no Git integration needed.

Manual upload projects are useful when you do not want to connect source control for app localization.

Who This Is For

Use manual upload when you need a simple iOS app localization workflow without repository access.

Common use cases:

  • Early testing before setting up source-control integration.
  • Teams with restricted repository permissions.
  • One-off localization passes on exported .xcstrings files.

Supported Uploads

Validation

Uploaded files pass strict validation before parsing, including UTF-8 checks and JSON structure checks.

Typical Workflow

  1. Export or collect the current .xcstrings file.
  2. Upload it to your project.
  3. Run localization processing.
  4. Review generated output and import it back into your app project.

Manual upload keeps the process explicit and controlled when you do not need automated pull request behavior.

Key Difference vs Repository Projects

Manual upload mode can prune localized rows that disappear from the incoming file payload, while repository mode favors preserving rows unless source keys are explicitly removed.

Expected Outcome

After a successful run, missing target-language rows are prepared and localized, and output stays parser-safe for iOS String Catalog usage.

Common Mistakes

  • Uploading an outdated file and expecting it to include recent source changes.
  • Treating manual upload as branch-aware (it is file-payload based).
  • Forgetting to re-upload after base-language edits.
  • Assuming missing rows will always be preserved even when removed from payload.