Your first visit
Choose an entry point that matches what you have.
Start with the content you have
- A few node links or a configuration you have already downloaded: open Node conversion.
- A subscription URL that you want the site to fetch: use Subscription conversion.
- A configuration you want to understand: try Node inspector. For renaming, filtering and deduplication, use Node table.
- Shared nodes to try: visit Free nodes. For software to install, start with Client downloads.
Use a workbench example to learn the interface first. Examples demonstrate the format; they are not working connections. With your own content, preview the result before copying, downloading or saving it. Leave advanced options alone until you need them.
When you need an account
Most local tools work without signing in. Personal subscriptions, site file management, favorites, discussions, check-in and node claims require an account. The public Subscriptions and File space entries lead to those workspaces. Repository tools also work without an account when you save the token in your own browser. Add regular tools to Saved tools for a shorter route back.
If you get no result
“Could not parse any nodes” and “could not connect” are different problems. Check the input and format for the first; investigate the client and network for the second. A configuration containing only rules cannot produce nodes. Split oversized inputs into batches. Local workspaces may clear when you leave or change account or language, so download results you need to keep.
Convert nodes for your client
Pick the client first, then the template and delivery method.
A normal conversion
- Paste URI links, Base64, Clash YAML or sing-box JSON into Node conversion. Use Subscription conversion for remote URLs, with a source User-Agent if needed.
- Choose the output for your client: Mihomo, Clash, sing-box, V2Ray, Surge, Surfboard, Quantumult X, URI or Base64. Clients support different protocols and parameters, so read warnings about skipped nodes and omitted fields.
- Choose basic output or a compatible template, check options such as UDP and name handling, and convert. The result window has configuration and node overview tabs, with search, copy, download and save-as-subscription actions.
Local processing, server previews and templates
Local mode converts node content in your browser. A server preview sends the selected input to the site. Remote subscriptions need server fetching; template dependencies may also require network requests as described on the page. Local conversion does not mean every template works offline.
Templates provide groups, routing and the configuration structure. Field mappings translate parameters. A base configuration supplies initial client settings; it is not a node-name prefix. Manage these in Conversion settings, Templates, Field mappings and Base configurations. Saved defaults apply to later conversions, without rewriting existing files.
With Clash/Mihomo, online rules are updated by the client. Inline mode fetches rules through the site and writes them into the configuration, which can take longer and create a larger file. If template preparation fails, retry or choose another template instead of relying on an old result. A successful conversion still needs a real connection check in your client.
Files or dynamic subscriptions?
One stores the current result; the other generates content when read.
Decide how updates should work
Saving a subscription file stores this conversion result. Editing or replacing the same file keeps its address, but changes at the upstream source do not rewrite it automatically. A dynamic link converts again when read, using its parameters and sources. Such links may contain source URLs, node content and access keys, so avoid posting them publicly.
For a long-lived subscription with several sources, sign in and open My subscriptions:
- Create one with a name, path, inline nodes or source URLs, then select the default format and template.
- Save, then choose “Validate and preview.” Check the node count and any errors; saving does not verify that a source works.
- Open “Show links” to choose and copy a format for this share. This leaves the subscription default unchanged. Manage expiry, enabled status, device limits and access logs in the workspace.
You can also save a standalone file from a conversion result without signing in. Its name is generated automatically; check the dialog for its lifetime and keep the link. Anonymous management credentials exist only on the current page. Refreshing, leaving, changing input or changing identity loses that management result, with no anonymous history list to recover it from. A read link cannot delete the file. Sign in before saving if you plan to update the same file over time.
Short links and cancellation
The icon at the end of a link field copies the full address. Supported links can use a site short link, with tt.vg available when configured. tt.vg receives the site alias. A shorter address is still a way to access the content; it does not make private information safe to publish. Use Short links to inspect, retarget or delete your aliases.
“Cancel subscription” in a saved-file dialog asks you to confirm the location, then deletes that file, including a repository file. It cannot erase copies already downloaded, third-party caches or Git history. To pause a managed dynamic subscription, disable it in the list instead.
For an empty response, check the preview and access log, then the key, expiry and device slots. A network change may count as another device. When content, price or revisions change, review the current selection instead of repeatedly submitting an old page.
Keep configurations in your file space
Manage content, sharing and access rules together.
Organize your files
My files has list and thumbnail views, name search and folders. Hover reveals actions; menus are available on touch devices too. Create text files, upload files, create folders or save a conversion result directly. A blank folder means the root. After saving, check the current folder and filters if something seems to be missing.
The save dialog offers My files, Site public files and connected repositories, and remembers the last destination in this browser. Review the replacement prompt when a name already exists in that folder. Replacing content preserves the address and settings. Moving or renaming normally preserves the subscription address as well. Review the scope of bulk and folder deletion carefully: deleting a folder includes its descendants.
Keep private links private
A private file uses the token in its address for access. Anyone with the complete link can read it without signing in as you. Set expiry, an allowed User-Agent and a device limit where needed. File details include successful and denied access and device records. After rotating a token, copy the new link into your client.
My public files contains the site public files you created. Use it for content you really intend to make public. These files do not have private-token or device restrictions; avoid placing configurations with passwords there by mistake.
If saving or reading fails
Check remaining space, file size and the specific error. On an editing conflict, keep your draft before reloading the current file. For denied access, check expiry, client restrictions, device slots and token rotation. If the stored content is missing, ask an administrator to check the actual file; a directory record alone cannot reconstruct it.
Connect GitHub, Gitee or GitLab
Choose where to keep the token, then how to share files.
Connect and work with files
Open GitHub, Gitee or GitLab and choose a token storage mode. Browser storage works without signing in and connects directly to the platform. Use your own device and disconnect when finished on a shared device. Account storage requires sign-in and keeps the token on this site, enabling site forwarding.
After validation, choose a repository and branch; this browser remembers the last selection. Browse folders and create, edit or delete files, checking the path and branch before committing. Read access does not imply write access. For a GitHub fine-grained token, select the target repository and grant repository Contents read and write access for file changes. Workflow changes may need an additional permission. Check the equivalent file-writing permissions on other platforms.
Original links or site forwarding
Original platform addresses are the default. A public raw link usually has no token. A private one may contain a token or temporary credential, and its holder may gain the repository access that credential allows. Shortening it does not remove that risk. If the original temporary address expires, its short link also stops working.
With an account connection, consent to site forwarding separately for each repository. This browser remembers the choice. Clients then fetch through the site without a platform token in the shared URL, but anyone holding that URL can still read the file. Unchecking consent does not revoke links already issued. Browser connections cannot use site forwarding, and credential-bearing browser links cannot be saved as site short links.
Self-hosted GitLab and troubleshooting
Enter the HTTPS instance base address without appending an API path. A different instance needs its own token. Browser connections need no administrator approval, but the instance must permit cross-origin requests from this site. Account connections automatically validate public HTTPS servers; private-network exceptions require administrator configuration. Check the instance, token expiry, repository scope and cross-origin error if connection fails. Missing folder statistics do not mean the folder is empty; open it to inspect its contents.
Inspect and organize nodes
Structure, location and network checks answer different questions.
Inspect first, organize next
Node inspector turns content into a node list, charts and explanations of connection parameters, with protocol and TLS filters. Its connection diagram explains the configuration without making a connection. Credentials are hidden by default. Revealing them may also include them in copies or exports, so check a report before sharing it.
Node table supports bulk name, address and port edits, append imports, selection across pages, sorting, full-configuration deduplication, deletion and undo of the previous edit. A field report is for inspection, not client import; use “Convert and subscribe” for a usable configuration. Connections with the same endpoint but different passwords or settings may remain. A reused endpoint is not necessarily an identical node.
Location and naming
Build names from a flag, country code, country name, number and original name. Choose “Look up locations and preview” before applying. The table looks up the entry IP's location, which may differ from the proxy exit; unknown locations keep their names. After a successful backend speed test, names may include both entry and exit, such as “🇰🇷_KR_韩国->🇩🇪_DE_德国.” Original names are retained, and rechecks do not automatically overwrite manual names.
Read connectivity results correctly
In Node connectivity, parse content, choose endpoints, review them and start the check. TCP/TLS measurements come from the site server, not your device. They do not verify proxy credentials or download speed. UDP is skipped and Reality receives a TCP check only. Free-node speeds come from separate backend kernel tests. Either kernel can qualify in dual mode, and the displayed figures come from one complete successful result.
For parsing errors, check UTF-8 and whether the input contains actual nodes. Unknown location still allows text renaming. For failed port checks, read the DNS, refusal or certificate reason before concluding that the node cannot work in any client.
Write rules and understand routing
Generate the configuration, then check your assumptions.
Generate or merge rules
Clash/Mihomo rules and sing-box rules offer rule-only output or merging into an existing configuration. Choose a rule type, enter values and a target, then arrange the order. Before merging, make sure the referenced group or outbound exists. Prepending, appending and replacing have different effects; check whether you still need the old rules before replacing them.
Account and site rules require an explicit read, preview and selection. Opening a tool does not replace your draft. Importing a local copy does not save it to your account; use the separate save confirmation to keep it there. The sing-box final outbound changes only when you explicitly choose to change it.
Inspect a configuration or many targets
Clash/Mihomo route inspector and sing-box route inspector inspect rules, target references, missing entries, cycles and fallback placement. Supply a domain, IP, network and port where relevant to see individual condition explanations.
For several destinations, use Batch rule debugger, with one target per line or the documented target JSON for more detail. It does not resolve DNS or invent an unspecified port or network from a URL. Results are static candidates. Rule sets, processes and other runtime conditions may remain indeterminate; a later match does not cancel the effect of an earlier unknown condition.
Inspect a local Geosite file
Geosite inspector reads a local Geosite.dat you select, showing categories, entries and attributes and checking literal domain matches. It does not download a database or execute regular expressions. Fix missing targets in the configuration. For indeterminate results, add the missing target information or consult the client's runtime logs rather than treating static analysis as a live traffic test.
Text utilities and client downloads
A few checks save time with both encoded text and software.
Encoding is not encryption
Encoding workbench supports Base64, URL, query-parameter and HTML-entity encoding and decoding. Choose the format and direction, enter content, convert and copy. Query parameters can be entered as key-value lines. A complete URL is processed as text, without visiting it. Convert again after changing input or options so you do not copy an outdated result.
Base64 is readily reversible and does not protect passwords. A plus sign in URL decoding may represent a space; a literal plus needs correct escaping. For unreadable text or decoding errors, check UTF-8, complete percent escapes and truncated Base64 rather than repeatedly encoding the same text.
Choose a client and package
In Client downloads, filter by device platform, then graphical or command-line interface and source. Read the project description. Details load recent GitHub releases where available, with stable or prerelease selection, platform, architecture and filename filters, plus expandable release notes.
One operating system may have separate x64 and arm64 packages, so check your device first. A recorded catalog version may not be current, and the recent-release list is not the full history. Retry a failed load or open the project's release page. If the architecture cannot be inferred from the filename, it remains unidentified; verify it at the source before downloading.
A catalog entry is not a software security certification. Download from the project you have checked, then follow its import, permission and logging instructions. If a configuration opens in the browser but fails to import, check the format, client version and link response before trying to re-encode the whole file.
Claim and contribute shared nodes
Read the measurement record, then confirm the cost and import method.
Choose and claim
Free nodes lists shared nodes that currently meet the directory conditions. Filter by name or protocol and inspect latency, speed, counts and measurement time. The display deadline is the current directory batch's validity, not the next test time. A historical speed does not guarantee a working connection now.
- Sign in and use the page's check-in button for the day's reward without leaving the directory.
- For one node, copy its URI or open its QR code for client import. These buttons claim directly and charge the displayed price, so read the points notice before clicking. Copy and QR reuse the claim for the same node revision on this page. The QR contains the full connection; treat screenshots as sensitive too.
- For a batch, selections carry across pages. “Select all filtered results” includes later pages, not just the visible rows. Check the format and displayed price before claiming links or generating a configuration.
Review the selection again if a revision changes. If a request's outcome is uncertain, retry the original request rather than starting another claim. For insufficient points, check in or inspect Point history; a balance error is not a conversion failure.
After a contribution
Submit fixed node content or one subscription URL at Share nodes, then follow review and import progress in My submissions. The optional source-description link is recorded without fetching it. Editing a contribution sends it back for review, and contributing does not automatically earn points.
Once an administrator enables the relevant tasks, approved fixed content is screened once; subscription URLs are fetched again at the configured interval. Existing protocol, server and port combinations skip screening. Nodes that pass TCP admission still need first speed tests and later rechecks. Import completion does not mean public listing. Failed, slow or changed-source nodes may be withdrawn. Contribute only connections you have permission to share.
Your account, points and security
Keep your preferences with your account and your access keys private.
Find your own content
Account overview brings together account information, usage and shortcuts. Use Points to check in and inspect rewards and spending. Article unlocks and node claims use the price displayed before the action. Plan and usage explains dynamic-subscription counts and storage allowances. Plan limits and file storage are separate: changing a plan does not automatically resize your file space. Disabled and expired saved subscriptions still count.
Set up sign-in methods
Account settings contains profile, password, two-step verification and available sign-in methods. Use the methods actually offered on the login page. Password, GitHub, Google, Telegram and Passkey availability depends on site configuration. A repository token connection is separate from GitHub sign-in and does not bind a login identity.
Keep your authenticator information safe and verify migration before replacing a phone. Add and test another sign-in method before removing an old one; the site protects the last usable entry. Password, email and sign-in binding changes may invalidate old sessions and require another login.
Common security questions
Use password recovery from the login page if needed. Check spam and the address if mail does not arrive, and never pass a verification code to another person. Follow the page's administrator-contact advice for unavailable login methods; repository tokens are not login credentials. Sign out on shared devices, and disconnect browser-saved repository tokens separately.
Account closure has a seven-day reversible period and still needs your final confirmation afterward. It does not automatically erase all history. Read the closure page before applying, and review your subscriptions, files and connections first. Closing an account cannot retrieve content already shared with others.
Articles, conversations and messages
Know where to read, ask questions and find your own history.
Read and save articles
Browse Articles by category, keyword or tag. Some need a password or points, and attachments can have separate conditions. Check the scope and price in the confirmation. A grant does not make an article permanently public: withdrawal or account restrictions can still affect access. Attachment access is checked again before opening; an external address you receive is not a permanently private link.
Save reading to Article favorites, and regular tools to Saved tools. These are separate lists. A favorite is not a purchase, subscription or saved copy of the body. If the source becomes unavailable, you may only be able to tidy up or remove the entry.
Discussions and feedback
Search Community for similar questions before posting in an appropriate category. Use a clear title and explain the steps, client and what you have tried. Discussion details provide a post stream, quotes, reply navigation and sharing. Check images and quoted content for secrets too. Manage your posts in My posts; edits may require review again.
For a tool defect, use its feedback action or visit Tool feedback. Track handling in My feedback. Processing notes may be public, so exclude tokens, private subscriptions and personal contact details.
Messages and notifications
Use Private messages for member conversations. Notifications collects replies, message alerts and site notices. Opening one checks current content permission before locating it, so a hidden or withdrawn post may no longer open. Refresh if the unread count has not caught up. “Mark all read” uses the displayed cutoff and leaves messages arriving afterward unread.
For administrators
Manage content, testing and publishing as separate workflows.
Find the right workspace
Start at Admin overview. Nodes and testing contains the pool, contributions, scans, tasks and executors. Content and community covers articles, posts and comments. Tools and conversion holds the catalog, clients and templates. Accounts, storage and site settings have their own groups. Preview the impact of a change, review its revision and provide a reason. Reload a conflict instead of overwriting another administrator's work.
Screening and rechecks
Node scans shows long-running task status, intervals and start/stop actions. Open settings for minimum speed, retries, consecutive failures, sources and kernel policy. Choose sing-box, Mihomo or dual mode where either can qualify. Nodes with TCP latency but no speed are prioritized, while existing nodes receive periodic rechecks. Failed or slow nodes are withdrawn; deletion after repeated failure depends on an explicitly enabled cleanup policy.
Use Detection tasks for queue, claim and result records, and Node pool to filter by status. Total, successful and failed attempts are separate; old history may not contain all failures. Executor monitor provides heartbeats, self-checks and errors. Executor workspace manages packages and configuration. A claimed task does not prove that a process is still online. Check recent heartbeats, errors and diagnostics rather than relying on old speeds.
Publish and schedule
Blogger and Telegram node push let you select currently valid nodes, preview the article or message, then send immediately. Schedules need their own settings and explicit enablement; saving configuration does not authorize real publishing automatically. Both share three subscription documents: Mihomo/Clash, sing-box and V2Ray URI. The first two use the site shared default templates; V2Ray URI has no routing rules.
Before sending, check the destination, expiry, template and public site address. Localhost links will not work for group members. Inspect records and permissions after a failure before sending again. Template edits affect newly generated links, without changing articles or messages already sent.