XRatio User Guide

Documentation.

Install the app, connect your client, and understand what each mode does.

Install XRatio.

The published build is for Windows x64. It includes its .NET runtime, so you do not need a separate .NET installation.

  1. Download XRatio.exe from the official release.
  2. Open the executable and follow the built-in Guide.
  3. Check the proxy status and listening address in the application header.
Choose a mode. Control (interception) changes the numbers reported by your existing torrent client, which still transfers your files. Simulation sends numbers to the tracker without transferring files or using a separate torrent client. Leave simulations stopped if you only want to use Control.

Connect your torrent client.

In qBittorrent, pause active torrents before changing the proxy settings. Open Tools → Options → Connection → Proxy Server. Menu labels can vary by client version and language.

Default local proxy settings
Proxy typeHTTP
Host127.0.0.1
Port3773
Tracker / BitTorrent communicationsUse the proxy
Resolve hostnames through proxyEnabled
Peer-to-peer connections through proxyDisabled

If you changed XRatio’s listening port, use the address shown in its header instead. Apply the client settings, resume the relevant torrent, then check Interception and Activity for the next announce.

Other clients need support for an HTTP tracker proxy. Their peer traffic should keep its normal route: XRatio handles tracker announces, not torrent file transfers.

Enable HTTPS interception.

HTTPS interception requires explicit trust in the local certificate authority created for this XRatio installation. HTTP interception does not require this step.

  1. Open Platform in XRatio.
  2. Read the certificate information, then use the trust action and approve the Windows prompt if you choose to enable HTTPS interception.
  3. Check the next HTTPS announce in Activity. You can remove the local CA trust from Platform when it is no longer needed.
Without the required trust, HTTPS interception stays blocked. Independent simulation uses the system’s normal TLS certificate validation.

Create a simulation.

  1. Open Simulation and choose a .torrent file.
  2. Select an HTTP/HTTPS tracker from the torrent and choose a client profile.
  3. Set the upload and download speeds, initial progress, counters and variation.
  4. Add the session. Adding a session does not send a network announce.
  5. Optionally set Timer (minutes) under Stop, then select the session and press Start.

Start sends a started announce. Manual update requests another announce, and Stop sends stopped. Simulation reports counters to the tracker without transferring the torrent’s files.

Use the app only on services and torrents where you are authorized to do so. Tracker rules may prohibit modified or simulated statistics.

Find your way around.

Overview
Proxy status, tracked torrents, active simulations and reported upload.
Interception
Original and reported counters, ratio, peers, status and last announce for each torrent.
Simulation
Configure, start, update and stop independent sessions.
Activity
Proxy and simulation events, including failures and tracker responses.
Settings
Language, themes, reporting rules, logging and update checks.
Platform
Windows integration, tray/startup behavior and HTTPS certificate trust.

Updates and saved settings.

The packaged Windows app checks the official GitHub release at startup. An available update downloads the executable and its published SHA-256 checksum, verifies it, then replaces and restarts the application. Development launches do not replace themselves.

Your settings stay in %APPDATA%\XRatio. Configured simulations are saved in simulations.json and restored stopped. The proxy password is not persisted.

View the latest release and checksums ↗

Troubleshooting.

No torrent appears in Interception.

Check that the proxy is running and that the client uses the same HTTP host and port. Resume the torrent and wait for an announce, or request a tracker update from the client. Then inspect Activity for a received announce or an error.

HTTP works, but HTTPS fails.

Check the certificate trust state in Platform. HTTPS needs trust for this installation’s local CA. Read the Activity error before changing other settings.

The tracker’s ratio has not changed.

A local counter is not proof that a tracker accepted it. Check the outgoing announce, the response and any error in Activity. The tracker controls when it accepts and displays updated statistics.

My torrent is stalled.

Check the torrent’s pause state, file availability and peers in your torrent client. XRatio does not transfer files; a running proxy alone does not prove that peer transfers are working.

Still need help? Open an issue on GitHub ↗

About the website demo.

The interactive preview is an illustration in your browser, not the desktop app. It does not load torrent files, contact a tracker or change an account. Aster is a fictional tracker.

It starts with 4 GB uploaded and 10 GB downloaded: ratio 0.40. Decimal units are used (1 GB = 1,000 MB). One real second represents 60 simulated seconds, and an example announce is sent every 2.5 real seconds. At ratio 3.00 the demo completes. Pause freezes the session; Reset restores its initial state.

Try the interactive demo ›