DLogin
Windows 3.5.8 · Linux 3.5.6 · macOS beta 3.5.5 · Android beta

Download XDLogin

Install it, create a free account, and keep ten profiles for free, permanently. No card, no trial timer.

v3.5.8, released 14 October 2026, for Windows. Linux stays on 3.5.6 and macOS on 3.5.5 until their 3.5.8 builds are added. Android in beta.

Recommended for Windows

XDLogin Setup 3.5.8

Windows 10 (1809+) and Windows 11 · 64-bit · about 111 MB

Other platform? Windows · Linux · macOS · Android

Download for Windows or the portable build, which needs no install and no admin rights Not code-signed: Windows shows “Windows protected your PC”. Check the hash, then More info → Run anyway.

Official downloads come only from xdlogin.com and github.com/ftwsourav/xdlogin-releases. Anything else, including ‘cracked’ builds, is not ours. How to verify a download.

Windows Stable

Installer or portable build. Profiles launch in your installed Google Chrome, Edge or Brave. Chrome is the best fit: under Edge or Brave, the client hints still say “Google Chrome”. If none of the three is found, a profile doesn’t launch and says why. You can still choose the built-in engine in Settings → Network, with no address bar, no endpoint for Puppeteer or Playwright, and one language and WebRTC setting shared by every profile.

Windows 10 (1809+) or Windows 11 · 64-bit · Setup about 111 MB, portable about 111 MB

These builds aren’t code-signed, so the first time you run one, SmartScreen shows “Windows protected your PC”. Check the hash first, then click More info and Run anyway. In PowerShell: Get-FileHash .\XDLogin-Setup-3.5.8.exe -Algorithm SHA256
Verify SHA-256 checksums
XDLogin-Setup-3.5.8.exe816fe8006be7fa82189556dee6ee46ae45bc2b89d8c3f79b2fc0585650554bb0
XDLogin-Portable-3.5.8.exed022a1cad6cc5191e571ef30ca31ae3b4c13ba06964906359f959913af798477

Linux Stable

x86-64 AppImage, or a .deb for Debian and Ubuntu. Verified end to end on Ubuntu 22.04. Profiles launch in your installed Google Chrome or Chromium (apt and snap installs are both detected).

x86-64 · Google Chrome or Chromium installed

AppImage: chmod +x XDLogin-3.5.6.AppImage, then run it. Package: sudo apt install ./xdlogin_3.5.6_amd64.deb

Verify SHA-256 checksums
XDLogin-3.5.6.AppImagef84846c32f87fdb2ca47d74451e5034295ddf4dd90f90cde85acd9b4e7f22d49
xdlogin_3.5.6_amd64.debaa751154874aa95073162bb501d678ed8a54bbc1d3f3ffe1ea10c92eceb82bac

Shell: sha256sum XDLogin-3.5.6.AppImage

macOS Beta

Apple Silicon or Intel .dmg. Profiles launch in your installed Google Chrome, Edge or Brave. This first build is unsigned and not yet verified on real hardware by us, so please report anything odd.

macOS 12+ · Chrome, Edge or Brave installed

The build is unsigned. After copying to Applications, run once in Terminal: xattr -dr com.apple.quarantine /Applications/XDLogin.app then launch. Profiles run in your installed Chrome, Edge or Brave. Please report issues.
Verify SHA-256 checksums
XDLogin-3.5.5-arm64.dmg7cf2b8929b7ed61dd6e3672a8ea73283c648da7ab9ec661d787671097d0ccea3
XDLogin-3.5.5.dmg (Intel)61bb83335a0a912dad304cac5559866d5d1abe3443462b10f59d4e330e1c5224

Terminal: shasum -a 256 XDLogin-3.5.5-arm64.dmg

Android Beta

A native app that runs each profile in its own isolated WebView, inside a real browser: tabs, popups, downloads through the profile’s proxy, uploads, find in page, history, bookmarks and an identity panel. Since 1.3.0 you can keep up to four profiles open at once, each in its own process with its own proxy, timezone and cookies (Android 9 and newer; on Android 8.x, one profile at a time).

Android 8.0+ · v1.3.0-beta.1 · no desktop needed · same account as the desktop app

Android will warn about installing from an unknown source; allow it for your browser once, then open the file. Every release is signed with the same key, so a new version installs over the old one and keeps your profiles. The app doesn’t update itself: new versions appear here and on the changelog.

Sideloaded. Not on Google Play, which doesn't list this category of app.

Known limitation: sites can see this is an Android WebView app

Android's System WebView adds an X-Requested-With header naming this app's package to every request a profile makes. We tried the documented allow-list API and rewriting the header on the wire; neither works on the WebView versions we tested (151, and 153 when we re-tested). A third approach — fetching pages through the app instead of the WebView — ships turned off in Settings and is not yet measured on hardware; even if it works it could only ever cover page loads, never form submissions, because Android does not hand the app a request's body. Until the platform fixes this, we do not claim that Android profiles hide the app's identity.

What does present the profile’s device, verified on real hardware: the user agent, client hints, platform, screen, touch, timezone, Accept-Language, WebGL and canvas, and since 1.3.0 Web Workers loaded from a URL. Workers built from in-page code (blob: workers) and service workers still see the real phone.

Verify SHA-256 checksum
XDLogin-1.3.0-beta.1.apkcab2f5ca0eab47b7afa52544286f1b1a037c9ac0db7840db72dd2a41d9af2164

Every release, with the same hashes, is on GitHub: releases. The Windows installer, the AppImage and the .deb update themselves: they check GitHub for a new release, download it in the background and install it when you quit (the .deb asks for your password first). The portable .exe, the macOS builds and the Android app don’t; download the new version from this page.

Quick setup

Three steps to a running profile

The same three steps on every platform. Platform-specific notes live on the cards above.

01

Install

Run the installer, open the AppImage, drag the .dmg to Applications, or sideload the APK. If you want certainty, compare the file against its published checksum first.

02

Sign in

Create a free account inside the app. Your plan follows the account onto any machine; the profiles themselves stay on the device you made them on, unless you turn on encrypted sync (Pro and above). What the app does send us is listed in the privacy policy.

03

Launch a profile

Create a profile, paste a proxy or run direct, and click Launch. It opens as its own browser with its own fingerprint and cookies, and with a proxy, its own IP. Check it with the built-in fingerprint test.

Requirements

What each build needs

PlatformMinimumBrowser engine for profilesStatus
WindowsWindows 10 (1809+) or Windows 11, 64-bit, 4 GB RAMGoogle Chrome (best), Edge or Brave installed; a limited built-in engine only if you choose it in SettingsStable
Linuxx86-64, AppImage or .deb for Debian and UbuntuGoogle Chrome or Chromium installedStable
macOSmacOS 12+, Apple Silicon or IntelGoogle Chrome, Edge or Brave installedBeta, unsigned
AndroidAndroid 8.0+Built in: an isolated on-device WebView per profileBeta, sideloaded APK

Disk: about 500 MB for the app plus roughly 200 MB per stored profile. RAM: 4 GB minimum, 16 GB or more for 20+ profiles running at once.