Decrypt HTTPS Traffic in Fiddler: The Complete SSL/TLS Decryption Guide
A complete, step-by-step fiddler tutorial for HTTPS decryption — covering Fiddler Classic, Fiddler Everywhere, mobile pinning, TLS 1.3, and troubleshooting.
Fiddler is the de facto standard HTTP debugging proxy for developers and QA engineers — but its true power emerges only when you unlock HTTPS decryption. Without it, secure traffic appears as opaque tunnels, hiding API calls, authentication tokens, malformed headers, and subtle TLS handshake failures. This guide walks you through every step of decrypting SSL/TLS traffic with Fiddler — from certificate trust setup to advanced configuration for modern browsers and mobile apps.
Why HTTPS Decryption Matters for HTTP Debugging
Modern web applications rely almost exclusively on HTTPS. APIs, SPAs, and microservices communicate over encrypted channels by default. If your fiddler debugging workflow stops at HTTP, you’re blind to 90% of real-world traffic. Proper https decryption enables:
- Validating JWT or OAuth2 token payloads before they hit your backend
- Inspecting CORS preflight responses and
Access-Control-*headers - Diagnosing mixed-content warnings or HSTS enforcement issues
- Capturing WebSocket handshakes (
wss://) and TLS negotiation details - Reproducing and isolating TLS version or cipher suite mismatches (e.g., TLS 1.0 disabled servers)
Without decryption, Fiddler shows only CONNECT tunnels — no request bodies, no response headers, no timing breakdowns. That’s not debugging; it’s guessing.
Prerequisites: What You Need Before Starting
Before enabling https decryption, ensure your environment meets these requirements:
Fiddler Version & Platform
- Use Fiddler Classic v5.0.20234.59830+ (Windows) or Fiddler Everywhere v1.22.0+ (cross-platform). Older versions lack support for TLS 1.3 decryption and modern certificate pinning bypasses.
- Fiddler Everywhere requires a paid license for full HTTPS decryption — the free tier captures only HTTP.
System Trust & Permissions
- Administrator rights are required to install Fiddler’s root certificate into the Windows Trusted Root Certification Authorities store.
- On macOS/Linux (Fiddler Everywhere), you must manually import
FiddlerRoot.cerinto your system keychain and mark it as trusted for websites. - For Android/iOS testing, you’ll need to install the Fiddler certificate on-device — instructions vary by OS version and device management policies.
Browser-Specific Notes
- Chrome and Edge respect the system certificate store only if launched without
--ignore-certificate-errors. Avoid flags that disable cert validation during debugging. - Firefox maintains its own certificate store. You must explicitly import
FiddlerRoot.cerviaSettings > Privacy & Security > Certificates > View Certificates > Authorities > Import. - Electron apps (e.g., Slack, VS Code) often ignore system roots. Use Fiddler’s Electron Proxy Configuration workaround.
Step-by-Step: Enabling HTTPS Decryption in Fiddler Classic
1. Enable Decrypt HTTPS Traffic
In Fiddler Classic:
- Go to Tools > Options > HTTPS
- ✅ Check Decrypt HTTPS traffic
- ✅ Check Ignore server certificate errors (unsafe) — useful for self-signed dev servers, but disable in production debugging
- Click OK, then confirm the security warning
⚠️ Warning: This setting makes Fiddler act as a man-in-the-middle (MITM). Never enable it on shared or untrusted machines.
2. Install the Fiddler Root Certificate
Fiddler auto-generates FiddlerRoot.cer on first HTTPS decryption attempt. To trust it:
- In Fiddler Classic: Tools > Options > HTTPS > Actions > Export Root Certificate to Desktop
- Double-click the
.cerfile → Install Certificate → Choose Local Machine → Place in Trusted Root Certification Authorities - Restart your browser and any apps you intend to capture
If you see NET::ERR_CERT_AUTHORITY_INVALID after installation, verify the certificate appears under Trusted Root Certification Authorities in certmgr.msc, not Personal.
3. Configure Browser Proxy Settings
Fiddler listens on 127.0.0.1:8866 by default. Ensure your browser routes traffic through it:
- Chrome/Edge: Launch with
chrome.exe --proxy-server="127.0.0.1:8866" - Firefox:
Settings > General > Network Settings > Manual proxy configuration > HTTP Proxy: 127.0.0.1, Port: 8866 - Or use Fiddler’s built-in toggle: Rules > Automatically Authenticate + File > Capture Traffic (F12)
Test with https://httpbin.org/get — you should now see full request/response detail, not just a CONNECT line.
Advanced HTTPS Decryption Scenarios
Bypassing Certificate Pinning (Android & iOS)
Many mobile apps implement certificate pinning to prevent MITM — even with Fiddler’s root CA installed. To decrypt pinned traffic:
- Android (API 24+): Add
<application android:networkSecurityConfig="@xml/network_security_config">and configurecleartextTrafficPermitted="true"inres/xml/network_security_config.xml. Then installFiddlerRoot.cerin User certificate store (not System). - iOS: Use Frida or Objection to hook
NSURLSessionorSecTrustEvaluate. Alternatively, deploy apps via Xcode withNSAppTransportSecurityrelaxed inInfo.plist. - For React Native or Flutter apps, inspect
android/app/src/main/res/xml/network_security_config.xmlorios/Info.plistfor pinning logic.
💡 Pro tip: Use Fiddler’s Filters tab to isolate traffic by host (
*.api.example.com) before applying pinning workarounds.
Capturing TLS 1.3 & ALPN Negotiation
Fiddler Classic v5.0+ fully supports TLS 1.3 decryption — but only if the client supports it and doesn’t enforce strict ECH (Encrypted Client Hello). To verify:
- In Fiddler, select any HTTPS session → Inspectors > TextView → Look for
TLS 1.3 (RFC 8446)in theRawtab - If missing, check client TLS settings: .NET apps may require
ServicePointManager.SecurityProtocol |= SecurityProtocolType.Tls13; - For ALPN inspection (e.g.,
h2,http/1.1), enable Tools > Options > HTTPS > Show TLS Handshake Details
You’ll see negotiated protocol, cipher suite (TLS_AES_256_GCM_SHA384), and SNI hostname — invaluable for debugging gRPC-Web or QUIC-related issues.
Troubleshooting Common HTTPS Decryption Failures
| Symptom | Likely Cause | Fix |
|---|---|---|
Tunnel to host:443 with no child sessions |
Browser not routing through Fiddler proxy | Confirm proxy settings; test with curl -x http://127.0.0.1:8866 https://httpbin.org/get |
502 Fiddler - Connection Failed |
Fiddler can’t reach upstream server | Disable antivirus/firewall HTTPS scanning modules (they conflict with Fiddler’s MITM) |
403 Forbidden on all HTTPS requests |
Corporate proxy intercepting before Fiddler | Chain proxies: Configure Fiddler to use corporate proxy under Tools > Options > Gateway |
| Certificate errors persist after install | Certificate imported into wrong store | Re-import FiddlerRoot.cer into Trusted Root Certification Authorities, not Intermediate CA |
| Mobile app refuses connection despite cert install | App uses certificate pinning or Android Network Security Config | See mobile debugging tutorial for pinning bypass patterns |
Fiddler Everywhere: Cross-Platform HTTPS Decryption
Fiddler Everywhere offers near-identical https decryption capabilities on macOS and Linux — but with critical differences:
- No admin privileges needed for certificate installation (uses user keychain)
- Automatic certificate generation & import via Settings > HTTPS > Enable HTTPS decryption
- Requires explicit permission to capture traffic from protected apps (e.g., Safari on macOS Monterey+) — enable in System Preferences > Security & Privacy > Privacy > Full Disk Access
- Does not support TLS 1.3 decryption on Linux due to .NET runtime limitations (planned for .NET 8+)
To debug Node.js CLI tools (e.g., npm, curl, axios), set environment variables:
export HTTP_PROXY=http://127.0.0.1:8866
export HTTPS_PROXY=http://127.0.0.1:8866
Then run node my-api-test.js — Fiddler Everywhere will capture all outbound HTTPS calls with full body inspection.
Best Practices & Security Considerations
HTTPS decryption is powerful — and dangerous if misused:
- 🔐 Never enable Decrypt HTTPS traffic on public or corporate networks — it exposes all encrypted traffic to anyone who can intercept your local proxy port.
- 🧹 Clear Fiddler’s cache regularly (
File > Remove All Sessions) — cached credentials or tokens may persist across debugging sessions. - 📜 Log only what you need: Disable logging for sensitive domains using Rules > Customize Rules > OnBeforeRequest:
if (oSession.HostnameIs("bank.example.com")) { oSession['ui-hide'] = 'true'; }
- 🧪 Use Filters liberally: Under Filters tab, enable Use Filters, then set Show only the following hosts to reduce noise during API testing.
For enterprise teams, consider deploying FiddlerScript rules to auto-redact PII or mask auth headers — see our fiddler tutorial on custom request modification.
Conclusion: Mastering HTTPS Decryption Is Non-Negotiable
You don’t need to be a cryptographer to decrypt HTTPS in Fiddler — but you do need precision, awareness of platform quirks, and discipline around certificate trust. With this guide, you now know how to:
- Configure Fiddler Classic and Fiddler Everywhere for full https decryption
- Install and validate the Fiddler root certificate across Windows, macOS, and mobile
- Diagnose TLS version, cipher, and ALPN issues
- Bypass certificate pinning in common mobile frameworks
- Troubleshoot 90% of HTTPS capture failures before opening a support ticket
HTTPS decryption transforms Fiddler from a passive observer into an active debugging instrument — giving you full visibility into the encrypted layer where most real-world bugs hide. Combine it with more tutorials on performance analysis and browse HTTP/HTTPS Capture tutorials to build a complete HTTP debugging toolkit.
Still stuck? contact us — our team responds to debugging questions within 24 hours.