Sign in with your email to prepare books, approve project files, and launch BYOK translation jobs. Project Arachne stores your project files and series memory, but never stores your provider API keys.
Choose a project, then select translation languages when you launch a job.
You need an invited account, a DOCX manuscript, and your own provider keys for any live model work. Arachne does not save those keys for you.
Yes. Upload the manuscript text you actually want translated. Remove newsletter signup pages, store links, review requests, bonus-book ads, copyright pages, and other backmatter unless you intentionally want Arachne to translate those pages too.
Translate one representative test chunk first. Your provider dashboard will show the real cost for that test, and you can multiply from there by chunk count and language count. Arachne can estimate, but your OpenAI and Anthropic dashboards are the billing truth.
Only paste a key when Arachne asks for it on a job form. The key is sent to that one worker process and is not stored in your project history, saved to your account, returned by the API, or kept anywhere on our side.
No. Arachne is BYOK per job. You need to keep your own keys somewhere safe, set your own spending limits, and rotate or revoke keys from your provider dashboards if needed.
You do. Bring your own OpenAI and Anthropic keys. Those providers bill your account directly for the tokens used by your jobs.
Arachne will stop the job and show a billing or credits message in the job area. Top up or fix billing in your OpenAI or Anthropic account, then rerun the job. Arachne cannot add credits for you and does not keep your provider keys.
Yes. After you start a translation, the work runs on the Project Arachne server, not on your laptop. You can close the page, close your laptop, and come back later to check progress or final files.
Arachne keeps your Project Files with the project: style sheet, glossary, voice profiles, canon facts, title precedents, and dossier. Those are the working files you paid to create and need for reruns, review, export, and support. If you attach a book to a series/shared universe, approved glossary, voice, and canon files are accumulated into that series so later books can build from them. Separately, Arachne can save Translation Lessons after a run. If you keep lessons, Arachne asks you to associate them with a series/shared-universe name, even if that series currently has only one book. Series names can be selected from your existing list or typed in as a new series. Provider API keys are never saved.
Translation Lessons are not the project setup files. They are approved language-specific fixes and recurring decisions learned during translation, final review, and repair passes. Save them under a series/shared-universe name, or decline to save them after export.
After final review. Arachne does not promote a language run into reusable series memory until the final review choices are complete, because those choices decide which fixes and lessons are actually safe to reuse. Saving approved lessons to a project or series is deterministic and does not call OpenAI or Anthropic again.
Not from this beta screen. Once a live translation starts, Arachne cannot guarantee that provider charges will stop mid-run. If you urgently need to stop provider usage, disable or revoke the API key in your OpenAI or Anthropic account.
Yes. Arachne shows whether your job is queued or running. The server runs up to 8 model jobs at once; extra jobs wait their turn. You can close the tab and come back later because queued and running work continues on the Project Arachne server.
Privacy.com can be useful for setting spending limits on the card attached to a provider account. It is not required, but it is a practical guardrail.
Yes. If you get stuck creating API keys, setting limits, or understanding a provider dashboard, ask your usual AI assistant to walk you through the current screen.
Arachne gives you translated final markdown, not a finished store upload package. EPUB creation is a publishing-production step: you may need frontmatter, backmatter, links, copyright pages, retailer metadata, cover files, device checks, and language-specific formatting choices. Different authors, languages, and retailers handle those details differently, so you should make the EPUB in your normal publishing tool or with a formatter you trust.
Arachne can do a lot, but AI is still AI. Before you publish, do a final production pass. We recommend running the final markdown through another AI or tool to check that no English has snuck through, names are consistent, protected terms stayed consistent, and non-Latin-script languages did not accidentally mix Latin and translated character names.
If you already have official translated titles, subtitles, or series names, upload them with the CSV template before setup. Save it as CSV UTF-8. You can ask your AI to fill the template from your existing list, but tell it not to invent translations.
Arachne already uses language-specific punctuation and typography defaults. Most authors should leave those alone. If you have a deliberate house-style reason to deviate, add that note to the Project Style Sheet before approval.
Arachne uses language-specific style packs instead of treating every language like English with different words. Those defaults cover punctuation, dialogue marks, typography, regional register, and common market expectations. They are meant to be sensible publishing defaults for authors, not a claim that there is only one correct way to write in a language.
Arachne's Spanish is aimed at broadly readable Latin American Spanish, with a Mexican-friendly center of gravity. It avoids leaning hard into Spain-specific phrasing unless your project instructions ask for that. The goal is polished, natural Spanish that travels well for romance, fantasy, and commercial fiction readers across the Americas.
Arachne uses generalized Modern Standard Arabic for fiction translation unless a project has a specific reason to do otherwise. That keeps the work readable across Arabic-speaking markets. Dialect-heavy choices are avoided by default because they can make a translation feel local to one region and wrong for another.
Arachne uses French dash-style dialogue for contemporary fiction because it is common, readable, and avoids overloading the page with guillemets. French typography still matters: Arachne keeps French spacing and punctuation rules around colons, semicolons, exclamation points, and question marks.
Yes. Arachne uses publishing defaults that fit each target language instead of forcing English habits into every file.
Brazilian Portuguese targets Brazil, not European Portuguese. Simplified Chinese targets Mainland Mandarin style, while Traditional Chinese uses Traditional characters and Traditional Chinese punctuation. Japanese and Korean do not treat italics like English; emphasis, thoughts, and messages are converted into native-feeling conventions. Korean uses standard South Korean fiction style, with speech levels and honorifics handled carefully. Hebrew and Arabic are right-to-left languages, so Arachne preserves RTL direction, script behavior, and punctuation expectations instead of treating them like left-to-right English. Hindi uses Devanagari, with attention to formality and gender agreement. Greek uses Greek quotation conventions and transliterates names where the language pack calls for it.
If you have a known house-style reason to prefer a different convention, add that to the Project Style Sheet before approval.
Use it if the DOCX has typos, punctuation issues, cleanup needs, or light consistency problems. Skip it if the manuscript is already professionally copyedited.
Chunks are Arachne's working sections. They are not necessarily chapters. A short bonus scene might become six chunks even though it is only one scene.
Arachne will attach your current project and run context so you do not have to diagnose it yourself.
Review this step and take the next action.
Accept the changes you want, reject the ones you do not, then continue preparing the book.
Keep the entries you want Arachne to use, reject the ones you do not, and correct category, gender, translation choices, and notes before approval. For genderfluid or context-dependent characters, choose Varies / see note and put the exact rule in Notes.
Preview or download the selected Final Markdown.
Review the passages Arachne wants a human decision on before final files are treated as ready.