The catalog contains 150+ public tools spanning language translation, style rewriting, alphabet and script, and code conversion.
On a typical page, enter or paste text, choose the controls that fit the task, run the tool, and copy the result.
Some tools use fixed mappings for characters or codes; AI language translators use DeepSeek to generate an output from the text you submit.
Individual pages include examples, FAQs, and processing notes so you can understand what a tool is designed to do before using it.
Inputs and available actions vary by page, so a control shown on one tool may not exist on another.
Historical-language and fictional-style outputs are not authoritative. Important results require human review, with a qualified human reviewer for consequential use.
"Find the page that matches the job, follow its examples, and check the output in context."
The collection includes four broad tool groups, each with a different purpose and processing method.
AI translator pages use DeepSeek for language translation. The model generates wording from context instead of following a fixed character map.
Converters use defined mappings for alphabet forms, character substitutions, or encoding formats such as binary and Morse code.
Historical-language and style tools support exploration and drafting; compare unfamiliar forms with reliable sources before using them as references.
Tools open in a web browser with no installation. Available controls and processing depend on the page.
Maintain a catalog of single-purpose pages with clear inputs and outputs.
Each page focuses on one text task and pairs its controls with task-specific instructions and examples.
Instructions, examples, and controls are revised when a page's behavior or scope changes.
To report a broken result or unclear page, email support@gurutrans.app, published in the website footer. Include the page address and what happened so we can correct or improve it.
Every page names the task it handles and presents only the controls available for that task.
Examples and FAQs should match the page's actual input and output.
Pages distinguish fixed conversions from AI-generated translation where that difference matters.
The Privacy Policy explains when submitted text is sent to an external service.
Broken controls, confusing instructions, and misleading examples should be reported.
A report with the page address and a sample input helps identify what needs an update.