New language.
Same voice.
Translate dialogue, stories, app messages, and game text. Use uncensored, abliterated models and specify the tone, names, and formatting you need.
Try an example in chat, then edit it for your text.
English日本語Español中文한국어FrançaisDeutschPortuguêsItalianoРусскийالعربيةहिन्दीไทยTiếng Việt
A character name replacement and dialogue that keeps its angry voice.
Translation examples.
App messages, game text, a few lines of dialogue. Start with an example and adapt it to your project.
App messages for Mexico, with template variables and JSON keys preserved.
A game item description with preferred terms and color tags.
Names, tone, and formatting.
- Voice and tone
- Set the register, mood, and character voice in your prompt. Ask for the same meaning and intensity in the new language.
- Names and terms
- Ask for a character placeholder to become a name, or supply exact translations for recurring terms. For example: replace [[name]] with Akira, or translate 月之碎片 as Moonshard.
- Formatting
- Tell the model to keep app variables such as {{name}} unchanged, preserve game color tags, or match the original line breaks. Include the actual text and the rules your tool needs.
- JSON your app can use
- Translate app strings in batches or build a glossary as structured data. The API supports JSON mode and JSON Schema, so you can define the keys and fields your tool expects. See structured output in the API reference.
Before you
translate.
What models can I use?
SIS serves uncensored, abliterated open-weight models. Choose a model in chat or specify it in your API request. Give it the original text and your translation rules, then check the result against your preferred tone and terminology.
Can I keep formatting, line breaks, and placeholders?
Specify which placeholders should be preserved and which should be replaced. The Japanese example replaces [[name]] with Akira; the Spanish example keeps app variables unchanged. For games, include your engine's control codes and ask for matching line breaks. Check the result before importing it into your tool.
Can I get JSON batches and build a glossary?
Yes. Include stable IDs with your source entries and request a JSON object containing the translated entries. You can also request names, items, locations, or skills as glossary records. Use response_format with a JSON schema to constrain the output structure; check entry IDs, ordering, and terminology in your tool.
Which languages can I translate?
The example requests cover English to Japanese, English to Spanish for Mexico, and Chinese to English. You can specify other source and target languages in the prompt. Translation quality varies by model and language pair, so try a representative passage first.
Is there a separate translation endpoint?
Translations use the existing /v1/chat/completions endpoint. These are general-purpose language models; the instructions in your prompt define the translation task.
Can I try a passage without writing code?
Choose “Try this translation” on any example to open its full request in SIS Chat. Sign in, edit the request if you want, then send it. You can also start with your own passage. Use the API when you are ready to connect your tool or automate requests.
Try your own text.
Open chat to translate a passage, or get an API key for your application.