Sitemap URL Extractor
Extract every URL from a sitemap.xml file. Fetch a sitemap by URL (via a public CORS proxy) or paste the raw XML, and the tool returns one URL per line — ready to copy into a crawler, a spreadsheet, or a redirect mapping. Supports both <urlset> and <sitemapindex> formats.
Tip: in your browser open https://www.lightscreen.online/sitemap.xml, press Ctrl/⌘ + A then Ctrl/⌘ + C, and paste here. Parsing runs entirely in your browser — nothing is uploaded.
How Sitemap URL Extractor works
Sitemap URL Extractor parses sitemap.xml using the browser DOMParser and walks every <loc> element under <urlset> (or <sitemap> under <sitemapindex>). The result is one URL per line, deduplicated and alphabetised by default. Nothing is uploaded — the parser runs entirely in your browser.
How to use
Either paste a sitemap URL and click "Fetch sitemap", or paste the raw XML straight into the input box. Toggle "Sort alphabetically" and "Remove duplicates" to shape the output. The right pane updates live as you edit.
Frequently asked questions
Does the tool support sitemap indexes (a sitemap that points at other sitemaps)?
Yes. Sitemap indexes (<sitemapindex>) are recognised and their nested <loc> entries are extracted. The tool does not follow the links automatically — it surfaces each child sitemap URL so you know which file to fetch next.
My fetch failed. What now?
The fetch goes through a public CORS proxy (api.allorigins.win). Some sites block proxies, return 403 to non-browser user agents, or rate-limit unknown clients. When that happens, open the sitemap in your browser, view source, copy everything, and paste it into the input box. Parsing then runs locally.
Are <lastmod> and <priority> preserved?
They are read but not included in the output, which is just one URL per line. The underlying parseSitemap function returns lastmod/changefreq/priority per entry if you want richer data.
Is my XML or sitemap URL sent to a server?
Pasted XML never leaves your browser — parsing is 100% local. Fetched URLs are relayed through a third-party CORS proxy, so the proxy operator can technically see them. If the sitemap is sensitive, paste the XML instead of fetching it.
How many URLs can it handle?
On a modern browser, the parser comfortably handles sitemaps with tens of thousands of <loc> entries. The limit is browser memory, not the parser; outputs of a few megabytes render without issue.
Why are duplicate URLs removed by default?
Sitemaps sometimes list the same <loc> twice (canonical variants, trailing-slash mistakes). Deduplication gives you a clean list without manual filtering. Disable it if you want every occurrence.