Upload files

Who can do this

Uploading requires the User role. User Read-Only members can open and download existing files but cannot upload new ones. Importing a file into a shared feature additionally requires Admin.

The upload surface in Ronja is the conversation: you drop a file into a chat with Ronja and tell it what to do with it.

Upload a file

1. Click New Exploration in the sidebar (or open any existing exploration).
2. Drag the file onto the chat — or click the + attach button and choose File. Images can also be pasted straight from the clipboard.
3. Type what you want Ronja to do with the file — “import this”, “summarize this report” — and press Enter.

An attached data file waiting in the composer.

From file to table

Data files — CSV, Excel, Parquet — become tables:

1. Send the file with an instruction like “import this as a table”.
2. Wait for Ronja to import it into a table — inside a feature if you tell her which one, otherwise as a session table only this conversation can see. Tables created from uploads carry the Dynamic kind.
3. If it landed in a feature, open the feature’s hub and find the new table in the Tables section; open it to preview the data.

Supported formats and size caps

Type	Formats	Cap
Data files (become tables)	.csv, .tsv, .xlsx, .xls, .parquet — plus CAD: .step, .stp, .dxf	No fixed cap in the uploader
Images	PNG, JPEG, GIF, WebP	20 MB
Documents	PDF, DOCX, PPTX, DOC, PPT	100 MB
Text & code	Markdown, TXT, JSON, YAML, SQL, Python, and most other text formats	5 MB
Archives	.zip	Unpacked automatically when small — see below

Files over their cap are rejected on the spot with a message such as “Image {name} exceeds 20 MB limit”.

PDF documents have their text extracted page by page at upload, so Ronja can read and quote them in the conversation.

Note

Only about the first 50 KB of a text file is passed to Ronja, even though uploads up to 5 MB are accepted. When that happens, the file pill in your message shows a “truncated” badge.

Zip archives

Attach a .zip and Ronja unpacks it for you. Ronja can then read and import each file inside as if you had attached it separately — a zip of CSVs imports like twelve separate CSVs, a zip of scanned invoices reads like twelve separate PDFs — and the unpacked files land in Files alongside the archive itself, which is kept too. The same happens to a zip emailed to an automation.

Unpacking happens automatically while the archive is small: up to 25 files, 150 MB of contents, and at most 10 images. Packaging entries — folders, __MACOSX, .DS_Store, empty files — don’t count.

Above any of those, nothing is unpacked. Ronja reads the archive’s contents list instead — names, sizes, and file types — tells you what’s in it, and unpacks on request. Say “unpack all of them” for the whole archive, or name the ones you want. Ronja never unpacks part of an archive on its own: entries sit in a zip in whatever order they were added, so a handful of them is an arbitrary handful, and a total computed over 10 of your 40 invoices would look exactly like the right answer. When an unpack does come back short, the step in Ronja’s working log says so — “12 of 40 extracted” — rather than reporting the twelve as if they were everything.

A zip with more than 10,000 members is too large to list at all. Ronja says so and asks for the specific files you need, or for a smaller archive.

A few things stay closed:

• Password-protected archives are listed but can’t be opened. Ronja says so and asks for the password, or for the files unencrypted. A single protected file inside an otherwise readable archive is named as protected, not silently dropped.
• Files over their type’s cap in the table above are named but not attached — one 200 MB PDF inside a zip doesn’t fail the rest.
• A zip inside a zip isn’t unpacked. It arrives as a file; attach it on its own if you need what’s in it.

Looking for the files a workflow produced, rather than files you uploaded? Those live on the feature hub’s File outputs tab — see Features.