Arkian logo
Start free
Structured metadata

Generate structured metadata beside the multilingual work.

Arkian creates structured metadata from approved source content so titles, descriptions, keywords, topics, and context can travel with the strings, scripts, audio files, or packages they describe.

Open Arkian See fit guide
Input
Approved source
Output
Structured metadata
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

Metadata that belongs with the package.

Use Arkian when the job needs usable context, not loose descriptions written after the files are done.

Before Arkian
  • Content is ready, but metadata is separate.
  • Titles and descriptions need consistency.
  • The package needs context for review or delivery.
With Arkian
  • Arkian produces structured metadata with the job.
  • Context stays beside the language assets.
  • The output 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 option
  • Languages
  • Package context

Outputs

  • Structured metadata
  • Titles
  • Descriptions
  • Keywords
  • Topics
  • Metadata JSON
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

Add approved source.

02

Choose metadata depth.

03

Generate structured metadata.

04

Review it beside 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.

Metadata is treated as part of production output.

Useful beside strings, scripts, and audio.

Keeps context visible and inspectable.

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.

metadata.json
Generate metadata.json files beside multilingual deliverables.

Generate metadata.json files from approved source content and package them with multilingual deliverables.

Semantic metadata
Create semantic metadata from approved source content.

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

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