Frequently asked questions

Yes. Bring your logos, images, colors, and reference images, then describe the look you want. aq builds a custom scene around your direction. You can carry that style into matching alerts, chat, starting-soon screens, and other parts of your stream without starting from a fixed template.

Treat it as a first draft. Tell aq what to change, such as the layout, colors, spacing, animation, or how an alert behaves, and review the result in Studio. You can make focused revisions to the same scene instead of starting over. AI revisions use generation credits, so clear feedback helps you get more out of them.

You can create full layouts, transparent graphics, animated alerts, chat overlays, goals, timers, scoreboards, and interactive scenes. Each scene gets a custom control panel. Describe both the look and what should happen, such as an alert reacting to a supported stream event or a label your moderator can update during the show.

No. Ask aq to put the settings you change often into the control panel, such as text, colors, scores, or alert buttons. You can also ask it to make parts of the scene preview editable. Using those existing controls does not spend generation credits. Ask for an AI revision when you want a new design, behavior, or control.

Scenes run in OBS Studio and Streamlabs Desktop as Browser Sources, and in Meld Studio as Browser layers. Your broadcasting app keeps handling your gameplay, camera, and audio. Connect Twitch, YouTube, Kick, StreamElements, or Realtime IRL when you want your scene to react to supported events or live data. Each connection has its own capabilities.

Create and preview your scene in your browser. To display it live, copy its private Scene link into your broadcasting app and set the source dimensions to match the scene. aq itself needs no desktop installation. Direct control of OBS, Streamlabs, or Meld has an additional connection step, which the Qontrol guide walks you through.

Yes. Ask for the reaction you want and connect the account that supplies the event. That might be Twitch Channel Points triggering an animation, a YouTube membership showing an alert, or a StreamElements tip updating a goal. Use the panel’s test controls to rehearse the behavior in Studio before relying on real events.

It depends on the scene’s complexity and your hardware. Browser sources use resources, especially with lots of animation or media. Test the scene in your broadcasting app alongside your usual gameplay and camera setup. If it causes problems, describe what happens and ask aq to simplify or optimize the scene before you go live.

Yes. Qontrol gives you custom control panels for your stream. Use it in Studio or in your phone’s browser to change labels, update scores, trigger alerts, and use other controls you’ve asked aq to build. Connect your broadcasting app for scene switching and audio controls too. Sign in on your phone with an account in the same workspace. Broadcasting-app commands require an active trial or subscription; no separate phone app is needed.

Once remote control is connected, aq can help inspect and adjust your setup. In OBS and Streamlabs it can create scenes, install browser sources, fix their dimensions, and adjust visibility, positioning, and audio. In Meld it can control scenes, layers, effects, and audio, and update an existing Browser layer’s URL. Add new Meld scenes and layers in Meld itself.

Yes. A workspace owner on Pro can invite trusted teammates who have aq accounts. They accept the invitation, select the shared workspace in their own accounts, and open Studio to revise overlays or use their controls. Each teammate can copy the Panel link themselves for another device, just as the owner does. Workspace membership includes access to shared scenes and panels; a Twitch moderator badge alone does not grant it.

No. Revisions to the same deployed scene keep its Scene link, and the controls you built into that scene update it without another export. You can keep improving the overlay after adding it to your broadcasting app. Changes to a scene that is already on air can affect the broadcast, so coordinate edits with anyone helping you.

You get 600 generation credits each month to create and refine scenes, plus a two-week trial of live deployment and broadcasting-app control starting when your workspace is created. Basic is $15/month and Pro is $30/month for ongoing live access. After the trial, you can still create with your free credits, use Studio previews, and operate your overlay’s existing controls. Taking the overlay live or controlling your broadcasting app requires a paid plan.

No. Credits pay for AI generation and revisions. Previewing a scene, using its existing controls, and running a finished overlay do not spend generation credits. Live Scene links and commands to your broadcasting app need an active trial or subscription, but leaving your overlay on stream does not drain your credit balance.

AI generation and revisions pause until credits refill, you buy a top-up, or you upgrade. Your finished scenes and existing controls still work. A deployed overlay can keep running without generation credits while your live-access trial or subscription is active.

Paid monthly plan credits roll over for one additional billing cycle. Free monthly credits do not roll over. Credits are used in this order: free credits, current plan credits, rollover credits, then top-up credits.

Yes. Plan changes apply immediately, with billing and credits adjusted for your usage and the time remaining. You can cancel anytime. Any eligible refund is calculated from credits consumed and time remaining in the billing period, then returned to your original payment method. Using up the plan’s value can leave no refund due.