Pick or change a file format
Prerequisites
Section titled “Prerequisites”- Open a project where you can create and rename files.
- Keep one test file available so you can verify format changes end-to-end.
- For a new project, open New project, pick a preset/format family, and create the project.
- To change an existing file’s format identity, rename the file with a new extension (for example
.mdto.typ). - If Titan shows the extension-change warning, confirm it in the rename confirmation step.
- Reopen the file and confirm it now uses the expected editor flow for that extension in Markup formats.
- To convert content, open the file tree context menu and click Convert to….
- In the conversion dialog, choose the target format and run conversion.
- Open the generated output file and validate the content.
Verification
Section titled “Verification”- A newly created project opens with files matching the selected format preset.
- A renamed file uses the editor behavior tied to its new extension.
- Convert to… creates a new target file and leaves the source file in place.
- If the target is compilable, compile controls are available in Compiler, build, and preview.
If Something Goes Wrong
Section titled “If Something Goes Wrong”- Wrong editor opens after switch
- Recheck file extension and routing expectations in Markup formats.
- Rename is blocked
- Use a valid filename and avoid duplicates in the same folder, then retry.
- Conversion option is missing
- Confirm the file extension is convertible; Titan only shows Convert to… for supported source formats.
- Converted output looks incomplete
- Some constructs may not survive a round-trip between formats. Common areas of fidelity loss include tables with complex styling, footnotes, comments, tracked changes, equations, embedded images, and citation formatting. If fidelity matters for your work, test with a representative sample before committing.