folio.

IMPORTING / PRACTICAL GUIDE

Upload text folders and ZIP note directories

Bring your existing text collection into the editor while preserving its nested directory structure. Folio prepares supported files locally, lets you review the result, and uploads only after you choose to import.

Try it in your workspace →Explore shared documents

PUT IT TO WORK

Step by step

  1. Prepare supported UTF-8 text chapters in a folder or ZIP archive. Split very large documents into smaller text files instead of trying to import a binary book file.
  2. Sign in and choose Upload directory from the workspace sidebar. Select a folder or ZIP using the available picker.
  3. Review the proposed root directory name, nested relative paths and text previews. Selecting files alone does not upload them.
  4. Check the remaining allowance shown in the import dialog, then confirm the import. Files are sent in bounded batches rather than one enormous request.
  5. Open the imported directory preview. If a request failed, retry within the existing import state so already accepted paths are not unnecessarily imported or charged twice.

Text documents, not executable packages

The importer is designed for supported text documents such as Markdown and plain-text chapters. PDFs, images and executables are not imported as note bodies. ZIP extraction is preparation for text import, not installation of a program or a third-party editor plugin.

Unsafe paths, path traversal, invalid UTF-8 and prohibited text content are rejected. There are also file-size and expanded-archive safeguards to prevent an oversized archive from exhausting the browser or hosting account.

Understand the monthly allowance

Free accounts can upload 25,000,000 bytes of UTF-8 note text per UTC calendar month. The counter measures newly imported text after ZIP extraction, not the archive's compressed size. Month rollover uses UTC, which may differ from midnight in your local time zone.

Reading shared notes, installing a shared directory, editing existing notes and creating a private version by modifying shared text do not use this upload allowance. Reaching the upload boundary does not lock your existing workspace or stop shared search.

Large collections and partial imports

The current preparation safeguards include up to 500 files and 25 MB per preparation, plus individual chapter and request boundaries. These are operational limits, not a promise that every document under the monthly allowance can be accepted as one giant file.

Each batch is validated and accounted for as it is accepted. If a later batch fails, earlier successfully imported batches remain. Review the returned state before starting a completely new import. Closing the import dialog stops future batches, but does not roll back files that have already been accepted.

Keep in mind

Choose files deliberately. Uploads create private text files; do not include credentials, unneeded personal records or material you are not authorized to store.

Common questions

Does a 2 MB ZIP always consume only 2 MB of allowance?

No. The counter uses newly imported UTF-8 text after extraction. Compressed size is not the measure.

Will closing the dialog delete the batches already uploaded?

No. It stops later work; accepted files remain in your private directory.

Find a useful starting point.

Search the shared notes and directory collection, then open your own workspace when you are ready to work. Reading a shared document does not create a private file.