Best SingleFile Settings for Archiving News Articles
Use these SingleFile settings to save readable news articles for offline reference, handle slow pages, and understand what a saved HTML copy can preserve.
For most news articles, use SingleFile’s normal full-page save, keep its default cleanup settings, and make sure the article and any images you want have loaded before saving. The result is a self-contained HTML snapshot for offline reference. There is no official news-specific preset: publishers vary, so adjust settings only when a page saves poorly or you need to keep particular content.
SingleFile’s official project describes its core job as saving a complete webpage into one HTML file. The browser’s download folder is the default destination. The settings below follow the project’s FAQ and option help.
Recommended settings for a typical news story
| Setting | Recommendation | Reason |
|---|---|---|
| Save action | Save the whole page | Preserves the article in its page context. Save selected content only when you deliberately want an excerpt. |
| Remove hidden elements | Leave enabled | Part of the default cleanup intended to keep saved pages smaller. Disable if the article body or a needed element is missing. |
| Remove unused styles | Leave enabled | Reduces page size by dropping styles that do not match elements. Disable if the saved page looks broken or processing is slow. |
| Scripts | Leave blocked | Scripts are removed by default; they can alter rendering and may not work offline. |
| Save deferred images and frames | Enable when available and needed | Allows content loaded later in the page to be included. Wait for the story and images to appear first. |
| Destination | Browser download folder | The simple default for a personal offline copy. |
| Format | Single HTML file | One portable file is convenient for reading and moving between devices. |
These are starting choices, not a guarantee that every publisher page will save identically. The saved result reflects what SingleFile could capture from the page at save time.
Save a news article step by step
- Open the article in your browser and wait until the headline, article body, and images you care about are visible.
- If the article loads more content as you scroll, scroll through it so the full story and deferred images have a chance to appear.
- Use SingleFile’s ordinary page-save action. Choose selected-content saving only if you want a cropped excerpt rather than the full article page.
- Keep the normal cleanup options on for the first attempt. Use the default local download destination unless you have chosen a remote destination in SingleFile.
- Open the saved HTML file from your download folder, preferably offline, and check the headline, text, images, and layout.
- If something is missing or the save takes too long, use the targeted adjustments below and save again.
Adjust settings for slow or incomplete captures
If saving takes too long or uses too much processing time
SingleFile’s FAQ recommends trying these changes first:
- Turn off HTML content > remove hidden elements.
- Turn off Stylesheets > remove unused styles.
Those changes can reduce cleanup work, but may produce a larger file or retain more page content and styling. If the page has many frames or deferred images, disabling frame removal or deferred-image saving may also speed processing; some embedded content can then be absent.
If images or embeds are missing
Check that the content appeared in the live page before capture. News sites may defer loading images, frames, or other content until a reader scrolls. Enable the deferred-content option when needed and allow the page to finish loading; SingleFile does not document one waiting interval that works for every site.
If an interactive element matters
Only change script handling for a specific reason. The FAQ suggests unblocking scripts and, if needed, retaining hidden elements, unused styles, and the raw page content. This can preserve more of the original material, but does not guarantee that interactive features will work offline: those features may depend on the original site or its servers.
Profiles, formats, and destinations
Use a profile when you have found that a particular publisher repeatedly needs different settings. SingleFile supports saved profiles and automatic selection by URL. Create and verify your own profile; the project documentation does not describe a prebuilt “news article” profile.
SingleFile documents single-HTML and self-extracting ZIP output options, as well as destinations including GitHub, Amazon S3, Google Drive, and WebDAV. For ordinary offline reading, a local HTML file is the simplest choice. If you keep a growing personal archive, you can separately back up the downloaded files, for example to an external drive; this is optional and is not required by SingleFile.
Limits and preservation tradeoffs
- A saved page is a snapshot. It records what the browser capture process could see at that time; it does not promise a complete copy of server behavior, every live feature, or future revisions.
- Offline scripts may not work. Dynamic maps, menus, carousels, and other interactive elements can depend on scripts or network services that are unavailable in the saved file.
- Browser restrictions can intervene. SingleFile’s FAQ notes that browser security blocks extensions on certain domains.
- Personal page capture is not professional web archiving. The project FAQ says SingleFile is not intended as a professional web-archiving tool, particularly in academia, and points to tools based on the WARC specification for that purpose.
- File size and fidelity trade off. Cleanup usually aims to make pages smaller; keeping more content, styles, or deferred resources can increase the saved file and processing work.
Or skip the browser setup
For a screenshot of the article instead of a self-contained HTML copy, ScreenshotNeo returns a PNG, JPEG, WebP, or PDF from one API request. See the ScreenshotNeo API documentation. This does not replace SingleFile’s HTML archive; it gives you a visual record of the page.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpimport 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)const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
await Bun.write('shot.webp', res);ScreenshotNeo removes cookie banners, newsletter popups, and chat widgets before capture. Bot checks, blank pages, and failed loads are never billed. Its MCP server lets AI agents take screenshots. The Free plan includes 1,000 screenshots each month with no card; paid plans start at $5 for 3,000. Sign up for free and get 1,000 screenshots a month with no card.
Troubleshooting
| What you see | Likely cause | What to try |
|---|---|---|
| Article text is cut off | The page had not finished loading, or later content had not appeared. | Wait for the article to render, scroll through it, enable deferred-content saving if needed, then capture again. |
| Images or embedded frames are absent | They were deferred, blocked, or had not loaded when saved. | Let them appear first and enable saving deferred images and frames. Some resources may still depend on the live site. |
| Saved page looks different | Cleanup removed hidden content or styles that the page relies on. | Retry with removal of hidden elements or unused styles disabled, changing one option at a time. |
| Capture is slow | Cleanup, frames, or deferred resources require additional processing. | Disable hidden-element removal and unused-style removal first. If acceptable, turn off deferred-image saving or frame handling, knowing content may be omitted. |
| Menus, maps, or carousels do not work offline | Scripts were removed or the feature depends on the publisher’s servers. | For a specific need, allow scripts and optionally retain hidden elements, unused styles, and raw page content. Offline operation is not guaranteed. |
| SingleFile cannot save a page on a particular domain | Browser security may block extension access there. | Check the project’s browser-specific notes and use a page or browser context where the extension is permitted. |
| Can’t find the saved file | The destination may have been changed, or the browser’s download location is unfamiliar. | Check the browser download list and SingleFile’s destination settings. The default is the configured download folder. |
FAQ
Does SingleFile preserve the article’s publication date and author?
It saves the page content available to the capture process. Check the resulting copy for those details; the cited documentation does not promise that every publisher presents them in a uniform way.
Should I save only the article text?
Use selected-content saving when a compact excerpt is your goal. For a reference copy that retains the page’s context and structure, begin with the whole page.
Can I make the saved page behave exactly like the live site?
No setting guarantees that. Scripts, remote services, and browser restrictions can limit offline behavior.
Is a single HTML file enough for research or institutional preservation?
It can be useful as a personal reference snapshot. For professional web archiving, follow the SingleFile FAQ’s distinction and consider a WARC-based workflow.
