Importing documents

Import an existing project

In the editor, choose File → Import (.typ, .md or .zip)…. The dashboard also has an Import button, and accepts files dragged from your computer.

• Use a .typ file for a single Typst source document.
• Use Markdown to convert supported content into Typst.
• Use a project ZIP when your source needs multiple files or assets.

Drop a file onto the dashboard

Drag one .typ file, Markdown file, or project ZIP from your computer onto the dashboard. Other archive and conversion formats match those available through Import in your workspace. The maximum file size for dashboard imports is 50 MB.

• Drop on the dashboard background to create a document in the folder you are viewing.
• Drop on one of your folder cards or a breadcrumb to import into that destination. The folder highlights, and Drop to import a document shows the destination path before you release the file.
• Dropping on an existing document card still creates a new document in the current folder. It does not add files to or replace that document.
• Folders shared with you cannot receive new personal documents. Choose one of your own folders or the root Dashboard.

Tylor shows Importing “filename”…, then opens the new document. A single Typst file keeps its filename and becomes the main file; an archive uses the existing project import rules. Build bundles still show their package review before import.

Import one file at a time. To bring a source file and its images together, compress them into a project ZIP. Dropping a desktop folder directly, an unsupported file, or an oversized file shows an error. If an import fails after saving a document, check Dashboard before trying again.

The overlay disappears when you leave the page or cancel the drag. On a phone or with a keyboard, use Import to choose the file. In an open document, dropping files into Files adds them to that document; it is a separate operation from dashboard import.

Typst and Markdown ZIP imports support accented image and folder names, including archives created with Compress in macOS Finder. Finder’s decomposed accents are composed when its ZIP omits the UTF-8 filename flag, so names such as étape-relâchement.png match ordinary source references. Source text and image bytes are kept unchanged. An archive with conflicting filenames is rejected instead of silently replacing a file.

If an older import already shows garbled filenames, import the original ZIP again to create a new project. Existing imported projects are not automatically renamed; keep any later edits, or rename the affected files to match their source references.

Source-code files in a project ZIP or uploaded through Files open as editable text. This includes C/C++ and headers, Dart, Python, Java, Kotlin, Swift, Go, Rust, JavaScript/TypeScript, Ruby, PHP, Lua, R, Julia, shell scripts, SQL, and web sources such as HTML, CSS, Vue and Svelte. Compiled object files such as .o remain binary. This provides text editing, not code execution or language-specific tooling. If a source file was imported as binary before this support was added, reimport the original ZIP into a new project, keeping any later edits from the old project. For a project without real-time collaboration, you can also upload the source file again through Files to replace that file with its text version.

Conversion is a starting point. Inspect tables, equations, images, and references after importing; source formats do not always represent the same layout features.

Verify the imported document

1. Open the expected main file and check the project’s compile entry point.
2. Confirm that referenced images and bibliography files are present.
3. Check imports for local packages or public package versions.
4. Resolve diagnostics, then inspect the compiled pages.
5. Export and check a PDF before relying on it.

Word or LaTeX conversion options depend on server support. If the option is unavailable in your workspace, import Typst/Markdown or convert the document externally first.

Server conversion can read only the main document you upload. It cannot fetch remote images or read linked files, including other files inside a LaTeX archive. Embedded images in Word, OpenDocument, and EPUB files are still imported. Markdown and Typst project archives retain their uploaded images.

For LaTeX, combine \input and \include sources into one self-contained main file before importing. Add any linked figures to the new project afterward and check their paths. A conversion warning stops the import with a Document conversion failed message rather than saving a document with silently omitted included text. Linked images may remain as references without their files, so always check the preview and file list.

Bring dependencies with you

A source file can reference assets that were not included in the upload. Install the required fonts and local packages, or obtain a complete copy from the author.

For a shared Tylor document, Make a personal copy is designed to preserve its referenced local package snapshots.

Reimport a build bundle

You can import the ZIP from File → Download project… → Build bundle directly, either from the dashboard or the editor’s File → Import action. Older Tylor build bundles are also recognized.

Tylor shows an Import build bundle review before creating the document:

• The original document file layout and main file are restored. The outer document/ folder, Makefile, and build README stay out of the editor’s file list.
• Bundled local packages become independent This project snapshots. The imported document uses these versions, even if My library contains different code under the same name and version.
• Also add missing package versions to My library makes those versions available to other documents. Clear the checkbox to keep them only with the imported document. Existing library versions are kept unchanged.

Choose Import document, then check the preview. Required font files already in the bundle are preserved; account fonts that were not exported still need to be uploaded separately. The import creates a new document and does not overwrite the original. If the document was saved but could not be opened or placed in its destination, Retry opening document continues with that saved document instead of creating another copy. You can also close the dialog and find it on Dashboard. If the destination becomes unavailable during review, choose another folder and restart the import.

If you imported a build bundle before this support was added and see document/, packages/, and the Makefile in the file list, reimport the original ZIP to create a clean copy.

Server import limits

Server imports accept uploads up to 50 MiB. Archives may contain at most 2,000 entries, 100 MiB of expanded data and 50 MiB per file. Links, special files, encrypted ZIPs, duplicate paths and paths escaping the project are rejected. Conversions also have time and resource limits; when the server is busy, retry shortly. Split oversized projects before importing them.