Plain `.v2k`
V2K1|00|<payload>The app’s portable config package and its marketplace are built around the same `.v2k` payload.
In v2ray injector, `.v2k` is not just a file extension. It is the portable package that preserves advanced manual settings, including V2K and Socket Custom fields. The Store marketplace transports that same package, so exporting, saving, publishing, redeeming, and importing all follow the same core format.
What a `.v2k` file is
Protected `.v2k`
V2K1|01|<iv.ciphertext>
Meaning.
The `V2K1` header identifies the package format. A plain package stores readable JSON payload data. A
protected package stores encrypted content so the config can be distributed without exposing every field in
clear text.
What `.v2k` preserves
Manual transport fields
Host, port, SNI, security, transport choice, and transport-specific options are preserved.
Socket Custom
Payload, mode, strict handshake, delays, timeout, response matching, throughput, and chunk fields survive export/import.
V2K
Mode, host, path, timing, frame sizes, auth, PSK, AEAD, and the rest of the `v2k*` contract survive export/import.
Portability helpers
Host-like values can be masked with aliases such as [host] for more portable packages when the route allows it.
Editable import versus protected import
| Mode | What the user gets | Typical use |
|---|---|---|
| Editable import | The imported config remains editable in the Config screen and follows the normal manual workflow. | Sharing within a trusted team or moving your own config between devices. |
| Protected import | The imported config enters a lock-style flow where sensitive JSON-driven values remain hidden and direct editing is restricted. | Distributing a tuned config without exposing the entire raw setup. |
Extension rule.
The app only accepts files ending in .v2k for this import path.
What users can do from Config
Save only
Create a `.v2k` file locally without publishing it.
Publish only
Send the exported `.v2k` package to the Store marketplace without keeping a local file copy.
Save + Publish
Keep a local `.v2k` file and publish the same package to the Store in one flow.
What the Store marketplace does
Public listings
Users can browse published `.v2k` listings, search them, inspect details, and import them into the app.
Two access models
Listings can be open or protected by one-time PIN/token flows depending on the creator’s chosen publication mode.
Creator Studio
Creators can link an email, receive a fixed Publisher ID and Manage Token, publish listings, archive them, delete them, and generate PIN batches.
Same import pipeline
When a Store listing is downloaded or redeemed, the app still imports it through the same `.v2k` pipeline as a local file.
Open listings versus protected listings
Open listing
Any user with access to the public listing can download and import the package directly. This is best for public sharing, templates, and openly distributed routes.
Protected listing
The user needs a one-time PIN/token to redeem the `.v2k` content. This is better when the creator wants controlled access or limited distribution.
What Creator Studio is for
Email-linked publisher identity.
The marketplace uses an email-linked publisher identity with a fixed Publisher ID and Manage Token for
creator-side management.
PIN batch generation.
For protected listings, creators can generate one-time PIN batches and export them for distribution.
Creators manage access, not the app team.
Store listings do not mean the app developer operates or guarantees the route quality of every published
config.
When to use link import, `.v2k`, or the Store
| Option | Best for | Weak side |
|---|---|---|
| Direct link import | Quick personal onboarding from standard link formats. | Does not carry the full advanced app state like `.v2k` does. |
| Local `.v2k` file | Portable advanced config backup or direct sharing between devices. | Distribution is manual unless the creator uses the Store. |
| Store marketplace | Public or controlled sharing with discovery, listing metadata, and creator-side management. | Still depends on the trust and quality of the listing author. |
Important caveats for users
Protected does not mean universally trustworthy.
A protected `.v2k` listing can hide implementation details, but it does not automatically make the route
safe or operated by the app team.
The marketplace transports configs, not guarantees.
The Store helps discovery, packaging, and controlled distribution. It does not guarantee route quality,
seller identity, or long-term server availability.
Import rules still apply.
If a package needs a compatible catalog server, CDN type, or host alias resolution, the app still enforces
those checks before applying the imported config.
Need the protocol side too?
Open the V2K page if you want field-by-field transport guidance, or the Socket Custom page if your shared package is built around payload logic.