How do you handle API keys during live coding tutorials?

I've been creating more video tutorials lately, and I keep running into the same anxiety-inducing moment: that split second before I share my screen where I frantically scan for any exposed credentials.

You know the one.

Even with all my prep, I still find myself doing the mental checklist:

• .env file closed? ✓
• Browser tabs with dashboards minimized? ✓
• That terminal with the database connection string... where is it?

But here's what really gets me: the cognitive load of staying vigilant kills the flow state that makes live coding valuable in the first place.

I've tried a bunch of different approaches:

The "blur it in post" method

• Requires remembering to actually blur it
• Adds hours to editing time
• Still miss things occasionally

The "fake data" method

• Breaks the authenticity of the demo
• APIs don't actually work, so you're just... pretending?
• Viewers can tell something's off

The "start fresh every time" method

• Clean browser profile for every recording
• Logout of everything
• Manually swap in dummy values
• Takes 30+ minutes of setup per video

None of these feel right. The first lacks reliability, the second lacks authenticity, and the third is just exhausting.

What I actually want

I want to show REAL code connecting to REAL APIs with REAL responses. But I also want to sleep at night knowing my AWS keys aren't floating around the internet.

The dream workflow would be:

1. Record naturally without constant paranoia
2. Use real credentials that actually work
3. Have something automatically catch/blur sensitive data
4. Keep the demo authentic and educational

So... what's your workflow?

Seriously, I want to know:

• How do you handle this in your tutorials?
• Do you have a system that actually works?
• What mistakes have you made that I can learn from?
• Are there tools that make this less painful?

Drop your approach in the comments. I'm collecting workflows and would love to hear what's working (or not working) for other developers creating content.

---

P.S. - I've been testing out DataBlur for this exact use case. It's a browser extension that auto-blurs credentials during screen recordings. Still early days, but the concept of "record naturally, blur automatically" feels like the right direction. Anyone else tried it?