Downloads
Trigger file downloads and retrieve them from your browser sessions programmatically.
Uploads
Upload local files into browser sessions to interact with file input elements.
Screenshots
Capture full-page or element-level screenshots from your browser sessions.
PDFs
Generate PDFs from any web page rendered in your browser session.
When to use each
| Feature | Use when |
|---|---|
| Downloads | You need to retrieve a file the browser downloaded (PDFs, CSVs, ZIPs, etc.) |
| Uploads | Your automation needs to interact with a file input field |
| Screenshots | You want a visual snapshot of a page or element for debugging or verification |
| PDFs | You want to generate, download, or display a PDF from a web page |
How files are stored
Downloaded files are synced to Browserbase’s cloud storage automatically — you don’t need to configure a download path. Files are available via the API after the session completes. Screenshots and PDFs are returned directly in your automation code and saved locally, not stored in Browserbase cloud storage.Downloaded files are renamed with a Unix timestamp to avoid conflicts (e.g.
report.pdf → report-1719265797164.pdf).