-
Notifications
You must be signed in to change notification settings - Fork 32
Options and features
The options page is searchable: use the search box in the top bar to jump to a setting. Settings are stored locally and synchronized through the extension's settings pipeline where supported.
Define directories relative to the browser's default download directory. Use the visual editor for structured editing or switch to text mode for direct syntax.
- Drag rows vertically to reorder.
- Drop on the middle zone of a row to nest beneath it.
- Add
---for a separator and>namefor a submenu. - Add
// commentfor rule metadata or// (alias: Label)for display text. - Use Always ask where to save on one row when only that destination should
open Save As. In text mode, this is stored as
// (dialog: true)metadata. - Give a row an access key with
// (key: i), or a post-save tab action with// (tab: close)or// (tab: return)— close or re-activate the tab the save came from once the browser accepts it. Save In 4.1 adds the matching// (after: close-tab)and// (after: return-tab)spellings. - Use the live variable list to insert path variables.
WebExtensions cannot normally save outside the default download directory. A symlink inside that directory can point elsewhere, provided the target already exists.
Save media, links, selections, pages, and supported tab-strip targets. Configure link preference, save-dialog conditions, duplicate handling, shortcut-file formats, notifications, context-menu access keys, and the click-to-save gesture. Since Save In 4.1 this expands to multiple configurable gestures — modifier plus left, middle, right, back, forward, double-left, or long-left click, with a configurable long-press hold — and routing rules can tell them apart with the gesture: matcher.
Set Recent locations to show zero to five successfully used explicit destinations in the context menu. Recent locations survive background restarts, preserve destination-specific Save As behavior, and exclude private-window and rule-selected destinations.
Under Save as shortcuts, Save a source link beside downloaded media creates a shortcut next to media saved from the context menu or manually from Page Sources. It uses the selected shortcut format and routed media name. The sidecar bypasses routing, Save As, webhooks, and History so the media download remains the primary operation.
Quick save saves straight to the default destination without opening the folder list. Show only Quick save in the context menu goes further and removes the Save In submenu entirely, which is the only way to reach a save in one click: browsers collapse an extension's items into a submenu as soon as there is more than one. The trade is the rest of the menu — the folder list, Last used, and the other actions go with it.
Always save to the default destination stops click to save reusing whichever folder you last picked from the menu. It resolves the same destination Quick save does, so the two agree. A matching routing rule still wins.
Add an extension when the filename has none derives one from the server's
Content-Type, so an extensionless CDN or query-suffixed URL stops saving as a
file your system will not open. It is off by default: it is the one setting
that renames a save you did not ask it to rename, and answering it costs a
request to the site. It only uses a type Save In recognizes — an unknown type,
including the application/octet-stream a server sends when it does not know
either, leaves the name alone rather than inventing an extension for it.
Whitespace is trimmed from both ends of every folder and filename, including non-breaking and other Unicode spaces. Browsers reject a path component that begins or ends with whitespace, so such a save would otherwise fail or quietly drop the folder; a component made only of whitespace becomes the replacement character. Whitespace inside a name is untouched.
Tab-strip context menus work in Firefox and Chrome 150+. Older supported Chrome versions omit them.
Shortcut formats that produce a .url or .desktop filename are unavailable on
Firefox, which refuses to save them. See Firefox vs Chrome.
Dynamic rules can rename files or route them based on page, source, filename, media, menu, and initiation context. Since Save In 4.1 a rule can also end in exclude: true to stop matching saves without downloading, or add after: close-tab to close the save's source tab once the browser accepts it. Use the rule builder and template library for common cases, or edit text directly. The last-download panel shows current test data and live variables.
Ordinary browser-owned downloads can be recorded in Save In History. Chrome can also route matching downloads natively; Firefox offers an explicitly experimental cancel-and-replace path with important limitations.
See Browser downloads.
The Page Sources panel discovers page media, images, documents, and links. It supports filtering, type facets, sorting, previews, URL copying, direct or batch saving, automatic-rule drafts, and Save In context-menu actions.
See Page Sources.
History records saves locally with status, path, source, initiation context, mechanism, menu/rule metadata, and useful variables. Filter, sort, select a date range, choose columns, paginate, reveal completed files, copy saved paths or source URLs, or export comprehensive JSON/CSV/TSV data.
See History.
Advanced settings include an Appearance → Theme choice for following the operating system or forcing Save In's options, reference pages, and Page Sources to use dark or light colors. Advanced also includes filename sanitization, fallback fetching, scoped Referer rules, the persistent counter, backup/reset, and diagnostics. Optional Webhooks can notify a user-configured HTTPS workflow after a direct Save In download starts. External extensions can use the Download API only after their exact caller ID is entered under Approved extensions with Allow; approved IDs appear as removable rows, while an advanced line editor supports bulk changes. The empty default blocks all external downloads while leaving API discovery available. Rejected non-private callers appear under Pending approval with an Approve button, attempt count, request kind, and last-seen time. The rejected URL is never stored. The options page can also expose experimental WebMCP tools to compatible in-browser agents.
See Integrations, Firefox vs Chrome, Authenticated downloads and request context, and Troubleshooting and diagnostics.