{"id":101,"date":"2026-11-20T08:38:51","date_gmt":"2026-11-20T08:38:51","guid":{"rendered":"https:\/\/v2hubs.com\/blog\/?p=101"},"modified":"2026-11-21T12:35:39","modified_gmt":"2026-11-21T12:35:39","slug":"v2ray-node-a-no-nonsense-way-to-search-parse-and-manage-free-proxy-nodes-on-windows","status":"publish","type":"post","link":"https:\/\/v2hubs.com\/blog\/2026\/11\/v2ray-node-a-no-nonsense-way-to-search-parse-and-manage-free-proxy-nodes-on-windows\/","title":{"rendered":"v2ray Node: A No-Nonsense Way to Search, Parse and Manage Free Proxy Nodes on Windows"},"content":{"rendered":"<h1><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-large wp-image-104\" src=\"https:\/\/v2hubs.com\/blog\/wp-content\/uploads\/2026\/11\/20261120163830-1024x548.png\" alt=\"\" width=\"1024\" height=\"548\" srcset=\"https:\/\/v2hubs.com\/blog\/wp-content\/uploads\/2026\/11\/20261120163830-1024x548.png 1024w, https:\/\/v2hubs.com\/blog\/wp-content\/uploads\/2026\/11\/20261120163830-300x161.png 300w, https:\/\/v2hubs.com\/blog\/wp-content\/uploads\/2026\/11\/20261120163830-768x411.png 768w, https:\/\/v2hubs.com\/blog\/wp-content\/uploads\/2026\/11\/20261120163830-1536x822.png 1536w, https:\/\/v2hubs.com\/blog\/wp-content\/uploads\/2026\/11\/20261120163830-2048x1096.png 2048w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/h1>\n<h1>v2ray Node: A No-Nonsense Way to Search, Parse and Manage Free Proxy Nodes on Windows<\/h1>\n<p>If you have ever collected a dozen <em>vmess:\/\/<\/em> and <em>vless:\/\/<\/em> links from GitHub gists, pastebin pages and subscription URLs, you know how quickly it turns into a mess. Half of them are duplicates, one third are dead, and none of them are in a format your client actually wants. That exact chore is what <strong>v2ray Node<\/strong> is built for \u2014 a small, bilingual desktop and web tool that finds nodes, parses them into clean configurations, and hands you an import-ready list for v2rayN.<\/p>\n<p>It is worth being clear about the scope up front, because a lot of tools in this space overpromise. v2ray Node is <strong>a node search, parsing and configuration workbench<\/strong>. It does not ship a proxy kernel, it does not tunnel your traffic, and it does not fake latency numbers it has no way to measure. You gather and organize your list here, then paste it into a real client to test the connections yourself. That honest division of labor is, to me, the most likeable thing about it.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-large wp-image-103\" src=\"https:\/\/v2hubs.com\/blog\/wp-content\/uploads\/2026\/11\/20261120163655-1024x648.png\" alt=\"\" width=\"1024\" height=\"648\" srcset=\"https:\/\/v2hubs.com\/blog\/wp-content\/uploads\/2026\/11\/20261120163655-1024x648.png 1024w, https:\/\/v2hubs.com\/blog\/wp-content\/uploads\/2026\/11\/20261120163655-300x190.png 300w, https:\/\/v2hubs.com\/blog\/wp-content\/uploads\/2026\/11\/20261120163655-768x486.png 768w, https:\/\/v2hubs.com\/blog\/wp-content\/uploads\/2026\/11\/20261120163655-1536x972.png 1536w, https:\/\/v2hubs.com\/blog\/wp-content\/uploads\/2026\/11\/20261120163655-2048x1296.png 2048w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/p>\n<h2>What it does, and what it deliberately doesn&#8217;t<\/h2>\n<p>The workflow is short enough to learn in a couple of minutes. You point the app at some sources, hit search, and it crawls those pages, extracts every supported node link it can find, parses each one, and drops the results into a single table \u2014 automatically de-duplicated so you aren&#8217;t staring at the same server six times.<\/p>\n<p>The part that surprises people is what happens when you stop a search early. It keeps whatever it has already collected instead of throwing it away, and a search never clears the nodes you already have loaded. For a tool that can touch up to 120 pages per run, that &#8220;stop when it&#8217;s good enough&#8221; behavior is more practical than a forced wait for everything to finish.<\/p>\n<p>What it won&#8217;t do: connect through the nodes, run a speed test, or convert arbitrary Clash, Xray or sing-box config files. It is a focused node manager, not a universal config converter, and it tells you the truth when a protocol or plugin it doesn&#8217;t understand shows up rather than silently mangling it.<\/p>\n<h2>Searching and importing nodes<\/h2>\n<p>There are two ways to get nodes in, and you will likely use both.<\/p>\n<p>The <strong>search side<\/strong> reads from sources you manage yourself. You can list GitHub repositories as <code>owner\/repository<\/code>, add public web or subscription URLs, or switch on GitHub keyword search so the app discovers recently updated repositories matching a phrase. Everything runs through the public, unauthenticated GitHub API by default, so occasional rate limits are normal \u2014 the built-in search log shows you which sources returned nodes and which failed, instead of just going quiet.<\/p>\n<p>The <strong>import side<\/strong> is for the pile of links you already have. Paste a blob of share links, a Base64 subscription, a Clash YAML\/JSON block, or a JSON backup exported earlier, and it parses them in place. On Windows the desktop app uses a native file picker bound to the window, so <em>Choose file<\/em> behaves like any other Windows dialog. The per-file and per-response ceiling is 5\u00a0MB, and cancelling a file choice or a failed read never wipes what you had already loaded.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-large wp-image-102\" src=\"https:\/\/v2hubs.com\/blog\/wp-content\/uploads\/2026\/11\/20261120163707-1024x656.png\" alt=\"\" width=\"1024\" height=\"656\" srcset=\"https:\/\/v2hubs.com\/blog\/wp-content\/uploads\/2026\/11\/20261120163707-1024x656.png 1024w, https:\/\/v2hubs.com\/blog\/wp-content\/uploads\/2026\/11\/20261120163707-300x192.png 300w, https:\/\/v2hubs.com\/blog\/wp-content\/uploads\/2026\/11\/20261120163707-768x492.png 768w, https:\/\/v2hubs.com\/blog\/wp-content\/uploads\/2026\/11\/20261120163707-1536x985.png 1536w, https:\/\/v2hubs.com\/blog\/wp-content\/uploads\/2026\/11\/20261120163707-2048x1313.png 2048w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/p>\n<h2>Protocols it understands<\/h2>\n<p>v2ray Node parses seven node types, both as standalone share links and inside common Clash configs, and it preserves the transport and security details that matter when the list is re-serialized:<\/p>\n<ul>\n<li><strong>VMess<\/strong> (Base64 JSON links)<\/li>\n<li><strong>VLESS<\/strong>, including Reality and other TLS query parameters<\/li>\n<li><strong>Trojan<\/strong><\/li>\n<li><strong>Shadowsocks<\/strong> (SIP002 and the older Base64 format, with plugin fields kept)<\/li>\n<li><strong>SSR<\/strong> (ShadowsocksR protocol, cipher and obfs parameters retained)<\/li>\n<li><strong>Hysteria2<\/strong> (accepted under both <code>hysteria2<\/code> and the <code>hy2<\/code> alias, including port-hopping details)<\/li>\n<li><strong>SOCKS \/ SOCKS5<\/strong><\/li>\n<\/ul>\n<p>WS, gRPC and standard TLS settings on the various protocols survive a parse-and-export round trip, which is the whole point: a node that came in with specific transport parameters should leave with the same ones intact.<\/p>\n<h2>Editing, filtering and working in bulk<\/h2>\n<p>Each node opens into a readable view with the full share link and the parsed JSON side by side, so you can see exactly what a configuration contains instead of trusting an opaque line. You can edit the friendly fields \u2014 name, server, port and credentials \u2014 through a form, or drop down to the raw link to adjust advanced transport parameters. Anything you save is re-parsed and validated before it is accepted, so a typo in a UUID or an out-of-range port gets caught at the editor rather than after import.<\/p>\n<p>The list scales sensibly when you have hundreds of nodes. Filter by name, server address, source or protocol, and sort by recency, name or type. The batch operations were thought through better than most tools in this niche:<\/p>\n<ul>\n<li><em>Select all<\/em> and <em>Invert<\/em> apply to every row in the current filter, including results on other pages \u2014 not just what&#8217;s visible.<\/li>\n<li><em>Copy<\/em>, <em>Export<\/em> and <em>Delete selected<\/em> apply to everything you&#8217;ve checked, even selections made outside the filter you&#8217;re currently looking at.<\/li>\n<\/ul>\n<p>Deleting is deliberately cautious. Removing a single node, a batch, or clearing the entire workbench each ask for confirmation, and the app nudges you to export a backup first. That friction is a feature when one stray click could otherwise erase a list you spent an afternoon assembling.<\/p>\n<h2>Getting your nodes into v2rayN<\/h2>\n<p>When the list looks good, there are three export shapes: plain <strong>share links<\/strong> as a <code>.txt<\/code>, a <strong>Base64 subscription<\/strong>, or a full <strong>JSON backup<\/strong>. Copy links straight to the clipboard or download a file, then import into your client. A couple of small, real-world touches stand out here \u2014 if the clipboard write is blocked (common in sandboxed or permission-restricted setups), a manual-copy window opens so you can select and copy yourself rather than losing the data. The app also links directly to the v2rayN client download and to an optional paid subscription page, and it opens both outside its own window instead of embedding random web content.<\/p>\n<h2>The Windows desktop app and the Store build<\/h2>\n<p>v2ray Node runs two ways. The web build is a local Node.js server you keep on your own machine, and the desktop build bundles the runtime so <strong>you don&#8217;t need to install Node.js at all<\/strong>. The packaged app keeps a normal Windows title bar, min\/max\/close buttons and resizing, with a light Mica backdrop on Windows 11 rather than a forced-fullscreen frame. It runs as a single instance, and to keep your saved nodes and settings predictable it uses a fixed local port and reuses the existing user-data directory \u2014 it won&#8217;t quietly hop to a different port and strand your stored data.<\/p>\n<p>The Store build is the tidy option for most Windows users: automatic updates, no SmartScreen warning about an unsigned executable, and a normal install\/uninstall lifecycle. The app stores nodes locally and, if you enable the optional <em>Save locally<\/em> toggle, keeps them as plain text in the app&#8217;s own data folder \u2014 something to think about on a shared machine, since node links carry UUIDs and passwords.<\/p>\n<p style=\"font-size: 1.15em;\"><strong>Ready to try it?<\/strong> Get v2ray Node free from the Microsoft Store here:<br \/>\n<a href=\"https:\/\/apps.microsoft.com\/store\/detail\/9PKC2SNV10S5?cid=DevShareMCLPCS\" target=\"_blank\" rel=\"noopener\">Download v2ray Node for Windows \u2192<\/a><\/p>\n<h2>A few limitations worth knowing<\/h2>\n<p>No tool is magic, and the constraints here are mostly sensible ones. A single run allows up to 40 sources, 120 page requests, three concurrent fetches, a 15-second timeout per request and a soft stop at 10,000 collected nodes. GitHub search uses the public API without a token, so heavy users can hit rate limits. Default public sources come and go \u2014 replacing dead ones is part of owning your list. And because it only reaches public HTTP\/HTTPS endpoints while refusing local, private and reserved addresses, it is a discovery and cleanup tool, not a way to route around anything it shouldn&#8217;t.<\/p>\n<p>It is also worth repeating the big one: found nodes are not tested. A public list of nodes says nothing about whether they work, are fast, or are safe to trust. Verify everything yourself in v2rayN.<\/p>\n<h2>Frequently asked questions<\/h2>\n<h3>Is v2ray Node free?<\/h3>\n<p>Yes. The app is free to install from the Microsoft Store, and the optional paid subscription link inside it is unrelated to the tool itself.<\/p>\n<h3>Does it work as a proxy client?<\/h3>\n<p>No. v2ray Node searches, parses, organizes and exports nodes. For actual connections and speed testing you import the results into a client such as v2rayN.<\/p>\n<h3>Do I need Node.js to run the desktop app?<\/h3>\n<p>Not for the packaged Store version \u2014 the runtime is bundled. Node.js is only required if you choose to run the web build from source yourself.<\/p>\n<h3>Which formats can I import?<\/h3>\n<p>Share links for VMess, VLESS, Trojan, Shadowsocks, SSR, Hysteria2 and SOCKS, plus Base64 subscriptions, Clash YAML\/JSON blocks, and JSON backups, either pasted or loaded from a file up to 5\u00a0MB.<\/p>\n<h3>Are my nodes saved online?<\/h3>\n<p>No. Everything runs and stays on your device. Local saving is off by default, and turning it on keeps plain-text node data only in your own browser or app data folder.<\/p>\n<p>If you spend real time chasing, deduplicating and prepping free nodes, v2ray Node takes the tedious middle part of that job off your hands and gives you back a clean list you can act on. <a href=\"https:\/\/apps.microsoft.com\/store\/detail\/9PKC2SNV10S5?cid=DevShareMCLPCS\" target=\"_blank\" rel=\"noopener\">Grab it from the Microsoft Store<\/a> and point it at your favorite sources.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>v2ray Node: A No-Nonsense Way to Search, Parse and Manage Free Proxy Nodes on Windows If you have ever collected&#8230;<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[27],"tags":[28],"class_list":["post-101","post","type-post","status-publish","format-standard","hentry","category-v2ray","tag-v2ray"],"_links":{"self":[{"href":"https:\/\/v2hubs.com\/blog\/wp-json\/wp\/v2\/posts\/101","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/v2hubs.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/v2hubs.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/v2hubs.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/v2hubs.com\/blog\/wp-json\/wp\/v2\/comments?post=101"}],"version-history":[{"count":1,"href":"https:\/\/v2hubs.com\/blog\/wp-json\/wp\/v2\/posts\/101\/revisions"}],"predecessor-version":[{"id":105,"href":"https:\/\/v2hubs.com\/blog\/wp-json\/wp\/v2\/posts\/101\/revisions\/105"}],"wp:attachment":[{"href":"https:\/\/v2hubs.com\/blog\/wp-json\/wp\/v2\/media?parent=101"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/v2hubs.com\/blog\/wp-json\/wp\/v2\/categories?post=101"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/v2hubs.com\/blog\/wp-json\/wp\/v2\/tags?post=101"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}