What can Nativ do?

Nativ is a cultural-localisation platform for adapting copy, creative assets and media with workspace brand context. Its dashboard, creative plugins and developer tools expose different workflows. A file accepted in one interface is not automatically supported by every other interface.

Which Nativ interface should I use?

For exact MCP operations and examples, use the MCP workflow reference. For Python and TypeScript setup, start with Build with Nativ.

What files and outputs can I work with?

Choose the deliverable first. Translating editable source text and replacing lettering in a flattened image produce different kinds of output. The examples below describe specific paths, rather than universal format support.

The Automation file picker also accepts formats beyond this summary. Consult the current upload screen and API reference for the exact operation you plan to use. Acceptance alone does not establish which elements or application-specific features survive a round trip.

How do glossary, brand voice and translation memory apply?

Brand voice and style guides

Workspace guidance gives translation requests shared tone and style context. Through full MCP, use get_brand_voice, get_style_guides or get_combined_prompt to inspect the available guidance.

Translation memory

Source–target pairs provide reusable wording and provenance. A retrieved match is evidence to inspect, not automatic approval for a new context. Use search_translation_memory before generating, and save approved wording deliberately.

Request context

A brief explains the audience, placement and job of this specific copy. For example, distinguish a button label from a paragraph even if both contain the same word.

Glossary

Supply terminology in the field supported by the operation. Full MCP translate accepts inline CSV through glossary; translate_batch does not expose that parameter. A CSV uploaded to one plugin is not evidence it is attached to every other tool.

There is no universal precedence contract here that promises a glossary always overrides every memory match or style instruction. Remove conflicting guidance and verify a small request with the actual operation. The glossary guide includes a scoped CSV example. Updating workspace memory or guidance is distinct from training model weights.

Does dubbing also translate the visible design?

The audio workflow transcribes speech, translates the script and generates a target-language performance. Background-music handling, speaker voices and timing options belong to that workflow. Remuxing places audio with video; it does not by itself replace visible words, logos or artwork.

For editable motion graphics, use the published After Effects plugin and review supported text, image and soundtrack layers in the composition. The broader Nativ Video product has its own early-access scope. For silent on-screen copy, author the timed source rather than asking speech recognition to find words that were never spoken.

Check get_audio_capabilities for account processing limits and list_voices for available voices in the target language. A language configured for text does not guarantee an available voice. Cloning a voice requires ownership or speaker permission and the relevant consent/verification steps.

Are results automatically approved or published?

A successful generation returns a proposal. Applying it to a design, approving its wording, saving it in translation memory and publishing the finished asset are separate actions. Your custom application must implement the review gate it needs; an API response is not a universal approval lock.

Some connectors have a specific handoff: the WordPress workflow creates translated drafts, while Airtable has a reviewed writeback. The focused ChatGPT MCP tool requires explicit approval before saving exact wording to memory. Those controls should not be generalised to every external API client or automation.

Backtranslation and rationale can help investigate a result. They do not replace a target-language reviewer, prove cultural appropriateness or certify accessibility. Review the final design, file or playback experience as well as the words.

What limits and troubleshooting should I check?

Limits belong to the interface and account. The dashboard picker currently caps PPTX at 100 MiB, DOCX at 50 MiB and Excel workbooks at 25 MiB. These are selection checks, not promises of processing capacity. Hosted MCP has a separate 100 MiB media-download limit; local paths do not bypass backend or account limits.

Hosted tools need an accessible HTTPS media URL, including an unexpired signed URL. A local filesystem path, private-network URL or private chat attachment is not equivalent. Generated hosted artifact links expire after one hour; download approved results to your intended storage. See media inputs and downloads.

• Authentication: distinguish API-key, OAuth and host-plugin sign-in. A reachable server is not an authenticated workspace.
• Credits and duration: check current workspace usage and account capabilities before generation. No fixed per-call price or unlimited processing is implied.
• Failed or partial work: inspect the error and completed outputs before retrying. Do not invent missing results or assume retrying a generation is free.
• Fonts or layout: review inside the destination application. A character limit is not a rendered-width guarantee.

Use the MCP troubleshooting reference and connection diagnostic. For a production support or security commitment, consult Support, Security and Trust and your agreement rather than inferring an SLA from a feature page.