How to Save a Webpage with SingleFile and Keep the Original Filename
Set SingleFile’s filename template to use a page’s title. If you mean the literal filename in the URL, the documented settings do not confirm a token for that.
To save a webpage with a recognizable name in SingleFile, open the extension’s options and set File name > template to a pattern such as {page-title}.html. This uses the webpage’s document title. If by “original filename” you mean the last segment of the page’s URL, the official material reviewed for this guide does not confirm a template token that preserves that literal URL filename.
That distinction matters: a page titled “Installation guide” could have a URL ending in /docs/install-v2.html. The title-based template can produce Installation guide.html; the sources do not establish that SingleFile can automatically produce install-v2.html.
Set a title-based filename in SingleFile
- Open SingleFile’s extension options from its toolbar button’s context menu. The project README describes choosing Manage extension in Firefox or Options in Chrome.
- In the options page, find File name > template.
- Enter
{page-title}.htmlto name saved files from the page title. - Save a page and inspect the downloaded filename. If you want distinct copies from different dates, the maintainer’s documented example is
{page-title} ({date-locale}).html.
SingleFile saves a complete webpage as a single HTML file. By default, the file goes to the browser’s configured downloads folder. The extension also offers other output formats; choosing a format and setting the filename template are separate choices. See the SingleFile README and its linked extension help for details that apply to your installed version.
What “original filename” can mean
| What you want to keep | What the reviewed documentation supports | What to expect |
|---|---|---|
| The webpage’s document title | Use {page-title} in File name > template. |
The downloaded name is based on the title, which may not match the URL. |
| The literal last filename in the URL | No URL-filename token is confirmed in the cited README or maintainer example. | Check the help bundled with your installed SingleFile version before relying on automatic URL-name retention. |
| The name of an existing local file | The sources reviewed do not establish a template behavior for retaining an existing file’s name. | Use the browser save flow or rename the downloaded file if needed. |
The documented maintainer example, {page-title} ({date-locale}).html, appears in a SingleFile discussion. It supports title and date placeholders; it is not evidence of a URL-path filename token.
Keep copies distinct and choose the output format
If you save multiple versions of a page, add the date placeholder shown in the maintainer’s example so each copy can have a date in its name. If you need a particular output format, choose that separately from the filename template. SingleFile’s project site describes the extension and its available formats, but options can differ among browser variants and releases. Check the installed extension’s options and help rather than assuming every browser exposes identical settings. See the SingleFile project website.
Troubleshooting filenames
| Symptom | Likely cause | What to do |
|---|---|---|
| The saved name uses the page title, not the URL’s final segment. | {page-title} refers to the page title in the documented example. |
Confirm whether title-based naming is acceptable. For exact URL-name retention, inspect the help bundled with your installed version; the reviewed sources do not verify a URL filename token. |
| The filename is not the template you entered. | The template may not have been changed in the active extension’s options, or the browser’s download flow may affect naming. | Reopen SingleFile’s options, check File name > template, save again, and inspect the browser’s download settings. |
| A save dialog changes the expected naming flow. | Browser download settings can affect how downloads are handled. A Chromium-specific interaction with “Ask where to save each file before downloading” is mentioned in a fork’s troubleshooting notes, but that is not a universal rule. | Check the browser’s download settings and the help for your installed SingleFile version. Treat that setting as a lead to investigate, not a guaranteed cause. |
| The options labels do not match these steps. | The README gives different extension-management labels for Firefox and Chrome, and browser variants or releases may differ. | Open the extension’s own menu or management page and use its linked help. SingleFile lists Chrome, Edge, Firefox, and Safari availability, but the reviewed sources do not establish identical settings across them. |
| The saved file is in an unexpected folder. | SingleFile uses the browser’s configured downloads folder by default. | Check the browser’s download location and download history. |
When a screenshot is the right output
SingleFile is for saving a webpage as a single HTML document. If you need a screenshot image or PDF instead, ScreenshotNeo provides a website screenshot API and MCP server for developers. A screenshot is a visual capture, not a replacement for SingleFile’s saved HTML page.
Or skip the browser setup
Make one GET request to capture a page as an image. Replace YOUR_API_KEY with your key and change the target URL as needed. See the ScreenshotNeo API documentation for request options.
cURL
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp
Python
import requests
r = requests.get(
"https://api.screenshotneo.com/v1/shot",
params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"},
timeout=90,
)
open("shot.webp", "wb").write(r.content)
Node.js
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
- Cookie and consent banners, newsletter popups, and chat widgets are removed before the shot; each cleanup step can be turned off.
- Bot checks, blank pages, timeouts, failed loads, and cache hits cost nothing. Response headers report the page verdict and billing status.
- An MCP server lets AI agents using Claude, Cursor, or another MCP client call
take_screenshot,get_page_info, andcapture_pdf. - The free plan includes 1,000 screenshots a month with no card. Paid plans start at $5 for 3,000 screenshots.
Sign up for ScreenshotNeo’s free plan and get 1,000 screenshots a month with no card.
FAQ
Does {page-title} preserve the original filename?
It uses the webpage’s title in the documented filename-template example. That title can differ from the filename at the end of the URL.
Can I add a date to a saved filename?
The maintainer’s example uses {page-title} ({date-locale}).html. Check your installed version’s help for the behavior available in your browser.
Is SingleFile available in more than one browser?
The project website lists Chrome, Edge, Firefox, and Safari. The available sources do not confirm that every setting is identical across those versions.
Does a screenshot replace the saved HTML file?
No. A screenshot gives you a visual image or PDF. SingleFile’s main purpose is to save a complete webpage as a single HTML file.


