Arkian logo
Start free
metadata.json

Generate metadata.json files beside multilingual deliverables.

Arkian creates structured metadata JSON from approved content so the package carries titles, descriptions, keywords, topics, and context along with the language assets.

Open Arkian See fit guide
Input
Approved source
Output
metadata.json
Control
Customer-owned
Metadata
01
{
"title": "Release Pack",
"keywords": [...],
"topics": [...],
"lang": "de"
}

Metadata files

Titles, descriptions, keywords, topics, and context in structured files.

CoreExtendedRich
Arkian multilingual production visual
structured packageoutput.zip
metadata-job/en/script.txt
metadata-job/en/metadata.json
metadata-job/de/metadata.json
manifest.json
Where it fits

Structured context for the package.

Use metadata JSON when language assets need context that can be reviewed, stored, delivered, or used by the next system.

Before Arkian
  • Metadata is written manually after translation.
  • Context differs by language or output type.
  • The package lacks a clear manifest.
With Arkian
  • Metadata is generated as part of the job.
  • Context stays beside the deliverables.
  • The package is easier to inspect and hand off.
Production outputs

Multilingual assets organized for review.

The customer brings approved source content. Arkian returns files organized for review, delivery, or release support.

String output
01
nav.homeHome
button.saveSave
error.retryTry again

String files

Localized copy with keys, placeholders, and file rules preserved.

JSONTS.stringsXMLYAML
Metadata
02
{
"title": "Release Pack",
"keywords": [...],
"topics": [...],
"lang": "de"
}

Metadata files

Titles, descriptions, keywords, topics, and context in structured files.

CoreExtendedRich
Voice output
03

Audio files

Translated scripts, approved narration text, MP3/WAV output, validation, and repair-ready language packages.

script.txtnarration.txtMP3/WAV
Language files
04
en/package.zip
fr/script.txt
es/narration.txt

Packaged assets

Predictable language folders, a root manifest, recorded validation status, and a downloadable ZIP for handoff.

FoldersManifestValidationZIP
Package preview

The package is the handoff.

Arkian keeps the output inspectable: named files, selected formats, language folders, and package context.

structured packageoutput.zip
metadata-job/en/script.txt
metadata-job/en/metadata.json
metadata-job/de/metadata.json
manifest.json

Inputs

  • Approved source
  • Metadata depth
  • Languages
  • Package settings

Outputs

  • metadata.json
  • Titles
  • Descriptions
  • Keywords
  • Topics
  • Context fields
How it works

A focused path from source to package.

The customer keeps control of the final system. Arkian prepares the multilingual assets and package structure.

01

Submit approved source.

02

Choose metadata options.

03

Generate metadata JSON.

04

Review it with the package.

Common jobs

For clear jobs that do not need a full localization stack.

Arkian can support apps, websites, voice prompts, kiosks, onboarding, support content, and other systems that need multilingual assets without a full CAT/TMS workflow.

Product builders

Localized app strings, metadata, help copy, release assets, and product-language files without connecting a repo.

Content teams

Approved scripts, articles, lessons, podcasts, and explainers turned into multilingual text, metadata, and voice files.

Small agencies

Client-ready multilingual packages without standing up a CAT/TMS, voice stack, metadata process, and file-prep workflow.

Customer-facing systems

IVR, voicemail, kiosks, SCO, EPOS, onboarding screens, support prompts, and other systems that need consistent copy or audio.

Operational teams

One focused multilingual job done cleanly: approved source in, structured output out, customer review stays in control.

Why it works

More than raw translation.

Translation is one part. Arkian adds the structure around it: formats, folders, metadata, scripts, voice files, naming, and delivery-ready packages.

Core, extended, or richer metadata can be scoped to the job.

Metadata travels with the output package.

Useful for systems that need context beside content.

Customer controls final use.

FAQ

Questions customers may have.

Is Arkian a CAT or TMS replacement?

No. Arkian prepares structured multilingual outputs from approved source content. Mature CAT/TMS platforms remain the better fit for translation memory, terminology governance, reviewer routing, and Git-native localization operations.

Does Arkian need repository access?

No. Arkian creates packages and files. The customer keeps their product, repository, CMS, IVR system, kiosk platform, or content system under their own control.

What does Arkian actually solve?

Arkian compresses the production work between approved source content and usable multilingual assets: strings, metadata, scripts, voice files, naming, folder structure, and downloadable packages.

Related workflows

Other Arkian workflows.

Metadata production
Create multilingual metadata that travels with the work.

Create structured multilingual metadata from approved source content for products, content, apps, and release packages.

Semantic metadata
Create semantic metadata from approved source content.

Create semantic metadata from approved source content, including topics, keywords, descriptions, and context fields.

Source to package
One approved source. Structured multilingual assets out.

Turn approved source content into structured multilingual strings, metadata, scripts, audio, and packages.

Start a focused job

Create the multilingual assets this job needs.

Choose the output path, review the estimate, and download a structured package.

Open Arkian
Arkian workflow visual