Guide Library Files

Library Files

Anything the AI creates for you — notes, outlines, CSVs, JSON, code, diagrams, calendars, and more — can be saved as a real file in your library instead of a one-off download. Each file gets its own page where you can preview it, edit it inline, chat with it, and use it as a source for any of Scholarly's AI tools.

What is a library file?

A library file is any text or data file that lives in your Scholarly library. It can come from:

  • Chat outputs — When AI Chat or Deep Research creates a file (a code sample, a CSV, a draft outline), one click saves it to your library.
  • Chat attachments — Text and data files you attach in chat (notes, CSVs, code, calendars) are saved as editable files automatically and stay around after the conversation ends.
  • Direct upload — Drop any supported text or data file into Scholarly the same way you would a PDF.

Once saved, a file shows up everywhere your other content does — Home, search, the sidebar, folders, and Pinned — each with an icon and color that matches its type at a glance.

Supported file types

Library files cover the everyday formats students and researchers use day to day:

  • Plain text and Markdown — .txt, .md
  • Spreadsheets and data — .csv, .tsv, .json
  • Code — most popular languages including Python, JavaScript, TypeScript, Java, C/C++, Rust, Go, and many more
  • Diagrams and vector — .svg, Mermaid diagrams, LaTeX
  • Calendars — .ics
  • HTML — rendered live in the preview

PDFs, Word documents, PowerPoints, images, audio, and video still live in your library too — they just open in their dedicated viewers. See Supported File Formats for the full list.

The file page

Open any saved file and you land on a focused page that shows:

  • A clean preview tuned to the file type — syntax highlighting for code, a real table for CSVs, rendered Markdown, an SVG canvas for diagrams, an event list for calendars, and so on.
  • A rename field so you can clean up the title.
  • The content options menu (download, share, move to folder, delete, restore) on the right.
  • A side chat panel where you can ask questions about the file.

Edit the file inline

For text-based files (Markdown, code, CSV, JSON, plain text, diagrams), click into the preview and start typing. A Saving / Saved indicator at the top tells you when your edits are written; click Save to commit changes immediately. There's no separate download–edit–reupload loop.

Chat with any file

Every library file opens with a side chat. Use it to:

  • Ask the assistant to summarize, explain, or critique what's in the file.
  • Clean it up — fix typos in a Markdown draft, reformat a CSV, tighten an outline.
  • Make changes you describe in plain English — "add a notes column", "rewrite the intro to be shorter", "translate to Spanish". The assistant's edits are saved straight back to the file, so you don't have to copy them out.

The chat sees the file you have open as its primary context, the same way chat from a PDF page is grounded in that PDF.

Save things you create in chat

Most files the AI generates inside chat or Deep Research now have a Save to library action. Click it and the file becomes a normal library item — opens in its own page, syncs across Home, search, the sidebar, folders, and Pinned, and shows up with the right icon and color for its type. From there it behaves like any other piece of content in your library.

Turn a saved file into anything

A saved file isn't just storage — it's a source for every AI tool in Scholarly. From a file's own Create with AI menu (and from any create modal), you can spin up:

The flow is the same as starting from a PDF, but you're working off your own notes, outline, code, or data instead of a pre-existing document.

Delete and restore

Files you no longer need can be archived from the content options menu. Archived files don't show up in Home, search, or your sidebar, but you can restore them from the file's page if you change your mind. Deleting a folder doesn't delete the files inside — they go back to your main content list.

Tips

  • Save your best chat outputs. If chat writes a useful CSV, code sample, or outline, save it to your library so you can return to it instead of scrolling back through a conversation.
  • Edit alongside chat. Open the file, ask the assistant for a rewrite or addition, and let it save changes straight back. The cycle is much faster than copy-paste.
  • Use saved files as study sources. A clean outline file is a great source for a podcast or video lecture. A CSV of formulas is a great source for a quick flashcard deck.
  • Keep a class folder. Group a unit's library files (your notes, AI drafts, formula sheets) with the PDFs and decks that go with them.
Was this helpful?
PreviousWorksheetsNextResponse Variants