Hiddify Guide
Hiddify Frequently Asked Questions: Find the Right Next Step
Use these short answers to choose the right Hiddify page before starting a longer installation, settings, or recovery task.
18 questions across 3 task groups
Downloads and releases
What is the latest Hiddify release?
The current official release API readback is v4.1.1, published on March 5, 2026. Treat that as a refreshable fact, not a permanent label. Open the page for your operating system to choose the correct asset. If v4.1.1 is already installed and the real connection works, do not reinstall solely for the version number.
Which Windows package should I use?
Use Setup x64 on most 64-bit Windows computers. Choose MSIX when packaged installation is required, or a portable archive when installation is not appropriate. Verify the architecture and exact filename before downloading from the official source. A correct choice should install, launch Hiddify, and expose the add-profile control.
How do I choose arm64, arm7, or universal on Android?
Choose arm64 for most recent Android phones, arm7 for some older devices, and universal only when the architecture cannot be confirmed. If Android rejects the APK as incompatible, return to the device information and choose again. Do not solve an architecture mismatch by downloading repackaged files from an unverified mirror.
Is an iOS package included in GitHub v4.1.1?
No. The current v4.1.1 GitHub release contains no iOS installer. iPhone and iPad users should use the App Store route referenced by the official README. If the app is not visible, check the OS version, Apple ID region, and network while preserving the store message; do not substitute an APK or desktop package.
Are accelerated download mirrors official?
No. The official GitHub release asset is the fact baseline. A third-party accelerated mirror may appear only after the exact filename passes current health and sample checks. A failed source must leave the active row, and the official source remains available. A mirror hostname must never be described as Hiddify official infrastructure.
Why verify SHA-256 after downloading?
SHA-256 checks whether the downloaded bytes match the digest supplied by the official release API. A completed transfer or plausible file size cannot prove that. If the digest differs, do not run the file. Delete that copy, return to the official source, redownload it, and verify both the filename and checksum again.
Installation and profiles
Should I install Hiddify before preparing a profile?
You may save the subscription URL securely in advance, but install and launch Hiddify before importing it. This keeps installation and profile failures separate. Continue when the dashboard exposes the add-profile control. A visible profile name and recent update time are the next results to check; otherwise recheck the URL rather than reinstalling.
Where do I import a subscription?
Open Add profile on the Hiddify dashboard. Read the complete URL from the clipboard or choose the manual entry path, then wait for a profile name and update time. Open the proxy list only after those appear. Treat the URL as sensitive and keep it out of public screenshots, logs, and support posts.
Why are there no proxies after import?
First determine whether the profile exists and whether its update time changed. Re-import a missing profile; refresh an existing one, then reopen the proxy list. If the update succeeds but the list remains empty, preserve that result and confirm the subscription content with the provider. Routing mode and TUN cannot create missing proxies.
Can I post my subscription URL when asking for help?
Do not publish a complete subscription URL because it can contain an identifier that grants access. Share a redacted error, platform, Hiddify version, profile state, update time, and proxy-list result instead. If the address has already been exposed, ask the provider to replace it; deleting the message does not revoke copied access.
Will an update preserve every existing profile?
No update can guarantee profile retention. Record the installed version, profile name, selected proxy, routing mode, and a recoverable subscription URL first. After updating, verify that the profile refreshes, proxies remain selectable, and the affected app loads a real page. Restore the previous package or profile before changing unrelated settings if one check fails.
Connections and routing
Does a connected status prove every app works?
No. A connected indicator only shows that Hiddify did not immediately report a failure. Keep the same proxy and load a real address in the target browser or app, then compare the disconnected result. If only one app fails, determine whether System Proxy covers it before deciding that TUN or DNS must change.
What is the difference between system proxy and TUN?
System Proxy is the lower-risk first choice for applications that honor operating-system proxy settings. TUN can cover more traffic, but adds permissions, DNS, routing, LAN, and other-VPN conflicts. Establish a working browser baseline with one proxy, then record the current state and test TUN only for a confirmed application coverage gap.
Is TUN required for a first connection?
No. Select one responsive proxy, enable System Proxy, and confirm a real page in the browser first. Use that as the reversible baseline. Consider TUN only when an affected app clearly bypasses System Proxy. Disable TUN and restore the recorded state if DNS, local-network access, or another VPN begins to fail.
Hiddify says connected, but the browser has no access. What next?
Keep one proxy and one test page fixed while checking the connection state, routing mode, System Proxy, and a fully restarted browser. Change one item per attempt. If access still fails, restore the original mode and enter connection troubleshooting instead of switching the proxy, DNS, and TUN together.
When should I change DNS settings?
Enter the DNS branch only when an IP address works but a hostname fails, or when Hiddify shows a name-resolution error. Record the original value, change one DNS option, and retry the same hostname. Restore it and return to proxy or routing checks if both IP and hostname fail or the result does not improve.
Should TLS Tricks be enabled by default?
No. TLS Tricks is an advanced branch for a specific handshake error after the proxy, routing mode, System Proxy, and DNS have passed. Save the original state, enable one option that matches the error, and retry the same target. Restore it immediately if the error remains or another failure appears.
What if I changed several settings and lost the cause?
Disconnect, restore the recorded proxy, routing mode, System Proxy, DNS, TUN, and inbound settings, then restart Hiddify. Begin again with the profile update time and proxy state. Keep one target fixed, change one control per attempt, and record the first setting that actually changes the symptom.
Already Have a Specific Symptom?
FAQ answers version, platform, and feature decisions. Troubleshooting starts from a visible symptom and provides the complete fix path.
Open the troubleshooting directory