Standard RSS, Atom, JSON and Other Feeds
The Local RSS/RDF/ATOM/JSON plugin stores feeds directly in RSS Guard. Use it when you want to subscribe to ordinary feed URLs without synchronizing through an online feed-reader service.
It is also the most flexible plugin. Besides normal web feeds, it can read local files, run scripts, import and export OPML, discover feeds from websites and apply network settings to individual feeds.
Add the Account
Open
Accounts -> Add account.Select
Local RSS/RDF/ATOM/JSON.Choose a title and icon for the account.
Optionally adjust Feed fetch spacing. A short delay between feed downloads can reduce load on servers and avoid starting every request at once.
Save the account.
When the account is empty, RSS Guard can offer to import data from RSS Guard 4, QuiteRSS or an OPML file. You can also load the bundled starter feeds or begin with an empty account.
Supported Sources
The plugin recognizes:
RSS 0.x and RSS 2.x
Atom 1.0
RDF/RSS 1.0
JSON Feed 1.0 and 1.1
Wordpress JSON Endpoint API for posts and pages
MediaWiki category and search pages, including Wikipedia
XML sitemaps, including sitemap indexes; compressed sitemaps when enabled by the build
iCalendar
Gemlogs
Normal feeds can be downloaded over HTTP or HTTPS. RSS Guard can also fetch feeds through the Gemini protocol.
Podcasts work like other feeds. Their media attachments can also be opened in RSS Guard’s media player when that feature is available.
Add and Discover Feeds
For the easiest setup:
Select the account or one of its folders.
Choose
Feeds -> Add item -> Add a new feed.Enter a feed URL or the address of a website.
Select the discovered feeds you want to add.
You do not always need the exact feed URL. RSS Guard downloads the supplied website, looks for advertised feed links and checks the resulting feed candidates.
The dialog accepts multiple addresses, one per line. Deep discovery can inspect links found in the supplied pages too, but it may download many pages and take noticeably longer.
Use Switch to advanced mode when you need to add one feed with custom source or network settings.
For a normal feed, enter its address in Source and select Fetch metadata. RSS Guard attempts to detect the format, title, description, encoding and icon.
Folders and Local Storage
Feeds can be organized into folders and rearranged freely. Articles, read states and account structure are stored in RSS Guard’s own database; they are not synchronized to another feed reader.
RSS Guard labels still work, but they remain local for this account.
OPML Import and Export
The standard plugin can import and export OPML files. Open the account menu and choose its import or export action.
During import you can:
choose the destination folder
select which feeds should be imported
fetch feed titles and icons
skip online metadata for a faster import
apply an optional post-processing command
Fetching online metadata can take some time for a large subscription list.
Export can include selected feeds, folder structure and feed icons.
Feed Sources and Processing
Most feeds use a normal URL, but the advanced feed dialog supports three source types:
URL downloads a remote feed.
Local file reads feed data generated or stored on your computer.
Script runs a command and reads feed data from its standard output.
An optional post-processing command can transform downloaded or generated data before RSS Guard parses it.
See Scripts, local files and post-processing for setup details and examples.
Full Articles and Comments
The Experimental feed settings include:
Fetch full articles to replace abbreviated feed contents with extracted website contents
Fetch in plain text to discard extracted HTML formatting
Fetch comments for articles when the feed and target pages expose supported comment links
Article date preference to prefer the published or updated timestamp
Report feed as broken when it contains no articles
Full-article and comment fetching performs extra downloads, so feed updates can take longer and the database can grow more quickly.
Per-Feed Network Settings
The Network tab can override application or account behavior for one feed:
connection timeout
HTTP/2 preference
cookie use
proxy and proxy credentials
additional proxy domains used by article resources in the
webviewerHTTP authentication
custom HTTP headers
A timeout of 0 uses the application-wide feed timeout. Other options that offer an application or account default behave similarly.
Ignoring cookies is useful when a feed must never share cookies accepted in RSS Guard’s built-in browser. Custom headers and authentication can help with private feeds, APIs or servers that require a particular request.
Additional proxy domains are mainly useful when article images or styles are hosted on a separate CDN. They affect proxy rules generated for the web viewer; see Proxy use.
MediaWiki category and search feeds
Warning
Log in to Wikimedia through RSS Guard’s built-in browser before refreshing many Wikipedia or other Wikimedia feeds. Use RSS Guard’s web variant and sign in on the wiki you subscribe to. The browser’s shared cookies let feed and API requests use that session. Keep cookies enabled in both application and feed network settings. Logging in only through an external browser does not share your session with RSS Guard.
The relevant Wikimedia API quotas, checked on 1 October 2026, are:
Mode |
Wikimedia limit |
|---|---|
Unauthenticated + compliant |
200 req/min |
Authenticated new/low-activity account |
200 req/min |
Authenticated established editor |
2000 req/min |
Authenticated approved bot |
Exempt from this quota |
Signing in with a new or low-activity account does not increase the 200 req/min quota. Established editors receive the higher quota. Approved bots still face operational limits. Quotas apply across Wikimedia projects and may change; other MediaWiki sites have their own policies.
Hitting a quota can produce HTTP 429 (Too Many Requests) and fail a feed refresh. Each article needs its own API request, so a refresh can consume several requests. Use a compliant User-Agent and avoid frequent bulk refreshes, even after signing in.
Paste a MediaWiki category page or a search results page into feed discovery. These Wikipedia and Gentoo Wiki URLs are examples:
https://en.wikipedia.org/wiki/Category:General_encyclopedias
https://en.wikipedia.org/w/index.php?title=Special:Search&search=quantum+computing&fulltext=1
https://wiki.gentoo.org/wiki/Category:Software
You can also paste a direct MediaWiki Action API URL into discovery or the advanced feed dialog:
https://en.wikipedia.org/w/api.php?action=query&format=json&list=categorymembers&cmtitle=Category%3AGeneral_encyclopedias
https://en.wikipedia.org/w/api.php?action=query&format=json&list=search&srsearch=quantum%20computing
Discovery and Fetch metadata convert these inputs to a canonical API URL and save it as the feed source. Category and search feeds include only main-namespace articles.
The category feed shows pages recently added to the category. The search feed shows matching pages ordered by their latest edit. Each result links to its article, and RSS Guard loads the rendered article HTML through the API. If any required API request fails, the whole feed refresh fails; RSS Guard does not download article web pages as a fallback. An article keeps the same feed item identity when it is edited. Search feeds watch a result set; they do not record every edit as a separate item.
Use fulltext=1 in a Wikipedia search URL so it opens a results page. Without it, Wikipedia can redirect a query directly to a matching article.
Each refresh loads up to five newest results plus up to five additional entries from a saved backfill cursor, with at most ten distinct articles. Categories backfill from oldest to newest; searches continue through their result pages. Progress survives restarting RSS Guard and advances only after the articles have been successfully processed and stored. Failed or cancelled refreshes retry the same backfill batch. At the end, another sweep begins so older articles are revisited. Changing the wiki, category or search query starts a new sweep. Search results can move between refreshes, and a wiki can limit the searchable result set, so changing searches cannot guarantee coverage of every result.
RSS Guard fetches each article’s HTML through a separate JSON API request. A refresh normally downloads one newest catalog page, one backfill catalog page and up to ten articles: up to twelve API requests. If invalid or duplicate results require more pagination, the newest catalog is limited to five pages, including the first response. With one backfill page and ten articles, the maximum is sixteen API requests per refresh; overlapping results or reused catalog pages reduce that count. Additional API requests are serialized and separated by a two-second pause. Several feeds or other clients using the same IP address or account can still share a server-side limit.
New MediaWiki feeds accept articles of any age so old backfill articles are not discarded by the application’s age cutoff. Existing feeds keep their settings; check Common settings if backfill articles do not appear. Explicit article filters and retention limits still apply, so traversing the whole catalog does not necessarily retain every article.
Useful Features
The standard plugin supports:
automatic feed discovery
manual feed and folder creation
OPML import and export
per-account feed download spacing
per-feed update intervals
conditional HTTP requests using server metadata
custom icons, titles and descriptions
podcasts and attachments (enclosures)
article filters, labels and queries
local files, scripts and post-processing
full-article extraction
per-feed authentication, proxy and request settings
Notes
This plugin does not provide two-way synchronization with another feed-reader service.
Moving the RSS Guard database or restoring a backup is how you transfer locally stored articles and read states.
A website can change or remove its feed without notice. Script-based sources can also stop working when an upstream page or API changes.
Only standard feeds are handled by the RSS Guard 4 and QuiteRSS import tools.