Migrating from Fiddler
Fiddler is two different products and you leave them for different reasons.
First: Classic or Everywhere
Fiddler Classic — Windows only, and since 3 August 2026 licensed for
personal, non-commercial use only: for commercial use Telerik points you at
Everywhere. It is not in active development, with no commitment to releases,
patches or support. It has FiddlerScript, AutoResponder, Composer, its own .saz
archive, and HTTP/1.x.
Fiddler Everywhere — Windows, macOS and Linux, by subscription, with HTTP/2.
There is no FiddlerScript in it: a Rules tab replaces AutoResponder.
If you are on Classic and the work is commercial, you have to move anyway and the only question is where. If you are on Everywhere, read the table below more carefully — Everywhere does more.
What maps to what
| Fiddler | Solpuga |
|---|---|
| AutoResponder (Classic) / Rules (Everywhere) | Map Local |
Breakpoints (bpu, bpafter) |
Breakpoints |
| Rules (Everywhere): header and body edits | Rewrite |
| Inspectors | Request and response inspector |
| Statistics | Per-phase timing and body sizes |
| Skip decryption for the following hosts | Bypass list, or SSL Proxying: selected hosts only |
| Bypass Fiddler for URLs that start with | Bypass list |
| Copy as cURL (Everywhere), cURL Script export (Classic) | Copy as cURL |
| Export Sessions → HTTPArchive v1.2 | HAR 1.2 export |
Import Snapshot → .har |
HAR import, read-only |
| Filters | Search, bodies included, and filters |
| Gateway | Partly: system proxy or PAC only, no authentication |
| WebSocket | Partly: messages recorded, none sent |
| Map Remote | Partly: via Rewrite |
| FiddlerScript (Classic) | Partly: Rewrite, no code |
| Composer | — |
| Replay | — |
| Reverse proxy | — |
| HTTP/2 (Everywhere) | — |
| Slow-network emulation | — |
.saz |
— |
Carrying sessions over as HAR
.saz is readable only by Fiddler, so HAR is the bridge.
In Fiddler Classic. File → Export Sessions → All Sessions (or
Selected Sessions) → format HTTPArchive v1.2.
Take v1.2, not v1.1: v1.1 cannot store non-textual response bodies. And know
about Classic's second limit: a .har is not compressed, so by default it stores
non-textual content only up to 32 kB. Larger images and files will not be in
the export — that is the exporter's setting, not Solpuga's.
In Fiddler Everywhere. Export sessions as HAR from the File menu.
In Solpuga. Tools → Import Session from HAR…
(Cmd/Ctrl + Shift + I), or open the file from your file manager. A separate
read-only window; a live capture keeps running. Files over 500 MB are refused.
What comes across
Headers, bodies, statuses, timings. The imported window uses the same inspector as a live capture: JSON as a tree, images with zoom, binary as hex; the raw message and the bodies can be written to files.
What is lost
- AutoResponder and Rules. HAR describes traffic, not settings. They get recreated; from a request in a live capture the rule is filled in with the response that actually arrived. The HAR window does not create rules.
- FiddlerScript. Not in HAR, and Solpuga runs no code. Simple changes have to be redone as Rewrite rules.
- Non-textual bodies over 32 kB — if the export came out of Classic with default settings.
- WebSocket. HAR has nowhere to put it.
- Double decompression. Bodies in Solpuga's HAR are decompressed while the
response headers are kept as they arrived; an importer that trusts
Content-Encodingwill try again.
What you get instead
Coming from Classic: builds for macOS and Linux, not Windows only, and no restriction on commercial use.
An interface in English and Russian, and a free tier with no time limit.
Tool for this page
HAR viewerOpen a HAR file and read the requests, headers, bodies and timings.Related
- Migrating from Charles Proxy to SolpugaA map of Charles's tools onto Solpuga's and how to carry a recorded session over as HAR: what travels, what is lost, and the limits.
- Migrating from Proxyman to SolpugaA map of Proxyman's tools onto Solpuga's and carrying a session over as HAR: what travels, what is lost, and the limits.