Solution for Blank/Slow Remote Debugging in CasparCG 2.5

Hi everyone,

If you’ve moved to CasparCG 2.5, you probably noticed that navigating to http://127.0.0.1:9222 now shows a blank white page. Additionally, using the standard chrome://inspect method can be very sluggish and slow.

I’ve created a simple Bookmarklet that restores the list of active templates and opens the debugger using your local browser, making it much faster.

How to use it:

  1. Create a new bookmark in your browser (Chrome/Edge).
  2. Name it Caspar Debug.
  3. In the URL/Location field, paste this code:
javascript:(function(){fetch('http://127.0.0.1:9222/json').then(r=>r.json()).then(data=>{let h='<style>body{font-family:Segoe UI,sans-serif;background:#111;color:#eee;padding:40px}h1{color:#6c5;border-bottom:2px solid #333;padding-bottom:10px} .item{background:#222;padding:15px;margin:10px 0;border-radius:8px;border:1px solid #444;transition:0.2s}.item:hover{border-color:#6c5;background:#282828}a{color:#4af;text-decoration:none;font-weight:bold;font-size:18px;display:block}small{color:#888;display:block;margin-top:5px}</style>';h+='<h1>CasparCG Templates</h1>';data.forEach(p=>{let l='http://127.0.0.1:9222/devtools/inspector.html?ws='+p.webSocketDebuggerUrl.replace('ws://','');h+=%60<div class='item'><a href='${l}'>${p.title||'No Title'}</a><small>${p.url}</small></div>%60;});document.body.innerHTML=h;});})();
  1. To use: Navigate to http://127.0.0.1:9222 in your browser first (it will be blank), then click your new Caspar Debug bookmark.

Did you try this method?
The odd thing that started happening on newer versions is that templates are now duplicated for some reason.

Yes, While chrome://inspect works, it’s often slow and fails to show templates immediately. Direct access via localhost:9222 (or whichever port is set in the casparcg config) was the fastest method in older versions, but newer CEF/Chromium restrictions have broken that functionality. This script bypasses those limits and makes the workflow fast again.