Build valid RSS 2.0 and Atom feeds from entered content items. Add titles, descriptions, dates, and links with XML output validation.
Type a channel name, link, and description, then add one row per post with a title, summary, date, and URL, and the tool emits the XML for a complete RSS 2.0 or Atom feed. It escapes special characters, converts dates into the format each standard requires, and validates the result as well-formed XML before showing it. The surprise for most users is that a feed is a static file you host: the tool produces the XML text, but you must save it, upload it to your site, and regenerate it whenever your content changes.
A concrete input and expected output from the current implementation.
Input
Channel: title 'Field Notes', link https://example.com, description 'Notes from the field'. Item: title 'Launch day', link https://example.com/launch, description 'Our first post & a sale', date 2026-08-16. Format: RSS 2.0.
Expected output
<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
<channel>
<title>Field Notes</title>
<link>https://example.com</link>
<description>Notes from the field</description>
<item>
<title>Launch day</title>
<link>https://example.com/launch</link>
<description>Our first post & a sale</description>
<pubDate>Sun, 16 Aug 2026 12:00:00 GMT</pubDate>
</item>
</channel>
</rss> The entered values land in the required RSS 2.0 elements, the ampersand becomes & because a raw & would break the XML, and the date is converted to the RFC 822 form the spec mandates - August 16, 2026 falls on a Sunday, hence 'Sun, 16 Aug 2026'. The result is well-formed XML that passes the tool's validation.
One set of channel fields (title, link, description) plus one row per item: title, description, date, link. These become the elements of your chosen format - RSS 2.0 uses channel and item with RFC 822 pubDate, Atom uses feed and entry with ISO 8601 updated. Empty fields follow the format's rules: an RSS item needs at least a title or description, an Atom entry requires id, title, and updated.
Every entered value is escaped before serialization, so ampersands, angle brackets, and quotes become the &, <, >, and " entities XML requires instead of breaking the document. The assembled output is then checked as well-formed XML and the offending element is pointed out if it fails. The result is plain XML text meant to be saved as a file and hosted by you - nothing is uploaded.
You get XML source text, nothing else. Save it as a file (feed.xml is conventional), upload it to your site, and link it from your pages so aggregators can find it. The tool runs entirely in the browser and uploads nothing; hosting and keeping the file updated are yours to manage.
That is the RFC 822 format RSS 2.0 requires for pubDate - the weekday and GMT timezone are mandatory parts of it. Atom instead uses ISO 8601 (2026-08-16T12:00:00Z), so the same date looks different in each format. A wrong weekday means the tool parsed the date differently than you intended.
The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Shorten URLs with local redirect tracking via localStorage. See click counts and generate a QR code for each link.
Build UTM-tagged URLs for campaign tracking with source, medium, campaign, term, and content parameters.
Enter 2+ headlines and see simulated previews in Google results, email subject lines, and social posts side-by-side.
Count characters for Twitter/X, LinkedIn, Facebook, and Instagram with platform-specific limits and warnings.
Calculate click-through rates from impressions and clicks with industry benchmarks and trend analysis.
Check email subject line length against best practices for desktop and mobile with preview text optimization.