Table of Contents
Server Profiles and Sharing
A server profile combines user-facing metadata with a backend connection configuration. Furious keeps those responsibilities separate so subscription ownership, test results, tags, and other profile metadata do not have to be embedded in a core-specific document.
Profile concepts
A profile contains two broad kinds of data:
- Metadata — remark/display name, stable profile identity, subscription ownership, test results, and stored annotations such as favorite state, groups, or tags.
- Connection configuration — protocol, address, port, credentials, transport, TLS, local proxy listeners, and backend-specific options.
The Home table presents both, but protocol plugins own parsing, validation, editing, and share-link serialization for their configurations.
Creating profiles
Open the Server menu on Home.
Structured editors
Choose Add VMess Server..., Add VLESS Server..., or another protocol-specific action. The available actions are discovered from installed protocol and editor capabilities rather than maintained as a fixed list in Home.
A structured editor validates and preserves the fields supported by that protocol. Double-click an existing row to open the corresponding editor.
Raw configuration
New Empty Configuration creates a profile intended for direct Furious JSON editing. The Advanced submenu provides Customize JSON Configuration... for an existing profile.
Raw editing is useful for backend features not yet exposed in a structured editor, but it bypasses many editor conveniences. Keep a backup and avoid changing the profile type to an unsupported value.
Importing profiles
The Import button on Home exposes these operations:
- Import Share Link From Clipboard accepts one or more newline-separated protocol URIs.
- Scan QR Code On The Screen decodes supported share URIs visible on the current display.
- Import JSON Configuration From Clipboard imports Furious profile JSON.
- Import From File... reads a configuration from a local file.
URI dispatch is scheme-based and plugin-owned. A malformed URI is reported by its protocol parser rather than being silently interpreted as another protocol.
Subscriptions reuse the same protocol handlers after a subscription decoder has produced individual items. See Subscription Management.
Managing the table
Select one or more rows and use the context menu to:
- move profiles up or down;
- duplicate or delete profiles;
- activate the selected profile;
- scroll to the activated profile;
- move profiles into a subscription group or back to manual profiles;
- edit raw JSON;
- share configurations.
Duplicate creates a new independent profile identity. If the source belongs to a subscription, the duplicate becomes a manual profile so a later subscription synchronization does not overwrite it.
Move To Subscription... changes group membership, not remote synchronization ownership. A profile moved into a group becomes a local member that survives later subscription updates. Moving a managed profile to another group also removes its former remote ownership.
The profile filter above the table can show All Profiles, Manual Profiles, or profiles belonging to one subscription, including its local members. Search accepts plain text or a regular expression and combines with that filter. Results update as you type; Enter or clearing the box applies immediately. Ctrl+F (Command+F on macOS) focuses the search box and selects the current query.
Testing profiles
Select the target rows, then open the Tests button on Home:
- Test Ping Latency checks ICMP reachability.
- Test Tcping Latency checks TCP connectivity.
- Test Download Speed runs supported profiles through temporary proxy-only runtimes, with multiple tests allowed concurrently.
- Clear Test Results clears the selected profiles’ saved test values.
- Stop All Tests cancels running and queued profile tests.
These actions are no longer in the table context menu. Ping and TCP results do not prove that authentication, routing, or proxy traffic works.
Activation and editing
The active profile is the one used by the next connection attempt. Starting a connection activates the single selected row. Selecting another row while disconnected does not by itself rewrite that profile's data.
Changing the routing selector while connected requests a controlled reconnection using the new routing mode. Editing connection fields generally takes effect on the next connection.
Sharing profiles
Share links
Choose Export Share Link To Clipboard for one or more selected profiles. Multiple links are separated by newlines. Export uses one canonical URI per supported protocol and preserves the protocol fields and remark that its codec can represent.
Current shareable protocols include VMess, VLESS, Shadowsocks, Trojan, SOCKS, Hysteria 1, and Hysteria 2. The corresponding parser handles hostnames, IPv4, and protocol-supported IPv6 forms. Reserved characters in credentials and remarks are encoded according to the protocol's URI format.
A profile may be valid for local use but not have a share-link representation. In that case no URI is produced.
QR codes
Choose Export As QR Code to process up to 50 selected profiles per window. Each successfully exported share URI gets a tab; profiles without a share URI or with a failed export are skipped. Tabs are generated incrementally, and closing the window cancels unfinished work. The full profile title is available as the tab tooltip when its visible title is elided.
QR codes contain the same URI produced by share-link export; they are not a separate configuration format.
Furious JSON
Export JSON Configuration To Clipboard serializes each selected profile’s connection configuration, with multiple JSON documents separated by newlines. It does not export profile identity, subscription ownership, annotations, or test results, so it is not a complete profile-store backup. JSON can preserve configuration that a share URI cannot represent, but it may include credentials, machine-local paths, and backend-specific fields. Review it before sharing.
External Core profiles deliberately have no public URI format and cannot be subscription items. Their internal JSON is machine-local and potentially executable; see External Core.
Credentials and privacy
Treat every exported URI, QR code, subscription response, and JSON profile as sensitive. Depending on the protocol, it may contain passwords, UUIDs, authentication tokens, certificates, public-key parameters, or local environment values.
Before posting diagnostics:
- reproduce the issue with the smallest relevant profile;
- remove credentials and subscription URLs;
- keep the protocol, transport, and non-sensitive error context;
- verify that logs do not contain data copied from an external program.
Subscription-managed profiles
A subscription profile records its source group. Synchronization may replace its connection configuration with the provider's latest item while preserving the profile identity and supported metadata.
For a lasting local variation:
- duplicate the subscription profile;
- edit the manual duplicate;
- leave the managed original available for future synchronization.
Deleting a subscription removes its remotely managed profiles. Local members of that group are kept and become manual profiles. Read Subscription Management before reorganizing a managed collection.