The name people see for Streamlabs Cloudbot comes from the account you connect as the bot; it is not a label you freely edit in the Cloudbot settings. To use a custom name, choose or create a separate bot account, authorize that account, and have Streamlabs Ultra, because custom naming is an Ultra feature rather than a free Cloudbot capability.
The key precaution is to make sure the platform authorises the bot account, not your main account. Streamlabs’ guide documents the name-customisation process for Twitch and says the same steps can be followed for YouTube. It does not document that workflow for Kick, even though Streamlabs lists Kick among Cloudbot’s supported platforms.
How Cloudbot gets its name
Cloudbot’s displayed identity follows the username of the account connected to it. When you connect a separate account intended for bot duties, its username is the name viewers see for the bot. That is why the process is not simply a matter of typing a new label into a name field: you are linking a different account identity.
This distinction matters because your main Streamlabs login, your YouTube or Twitch channel identity, and the account connected as Cloudbot may be different things. Start from the Streamlabs account that manages Cloudbot, but connect the separate account you have chosen for the bot. Do not authorise your primary channel account in place of the bot account if your aim is to have the bot appear under a distinct name.
Streamlabs’ Cloudbot name guide describes connecting an account and warns users to check which account is being authorised. Treat the username as the source of the bot’s visible name, and treat the connection step as the important change. This also means a later username change or account switch can affect what identity the bot presents; it is not an independent cosmetic alias detached from the connected account.
A useful way to plan is to decide on the bot identity before opening the authorisation window. If you run a devotional channel, for example, you might want a distinct account name that is clearly associated with the channel but is not your personal account. Check that the account can be accessed and that its name is suitable for viewers before linking it.
Create or choose a separate bot account
Use an account set aside for bot activity rather than your personal or primary channel identity. Streamlabs recommends a separate bot account in its guidance, and the practical reason is straightforward: it keeps the public bot identity distinct from the account you use to run the channel. It also reduces the chance that you accidentally connect the wrong identity while authorising Cloudbot.
If you already have a suitable separate account, use that one. Otherwise, create the account on the platform you intend to connect, using the platform’s current account creation process. Choose its username deliberately, because that username is what Cloudbot will use as its displayed name. Avoid creating multiple accounts in a hurry and then trying to remember which one is signed in when the browser opens the authorisation page.
Before connecting, confirm that you can sign in to this separate account and that you know which browser session is active. If you share a computer with other channel administrators, ask them to avoid leaving the primary account signed in on the same browser profile during setup. A password manager or a separate browser profile can help distinguish accounts, but neither changes which account the platform will authorise; you still need to verify the account shown by the platform.
Keep the account credentials secure and give access only to people who need to manage the bot identity. The guidance on securing your YouTube and streaming accounts is relevant here: a separate account is useful only if it is also maintained responsibly. Do not share passwords in a channel chat or in a public troubleshooting post.
There is no need to change your main channel’s username to rename Cloudbot. Changing that username would affect the identity of your channel account, while the Cloudbot setup uses the account specifically connected as the bot. If the name shown by the bot is wrong, first check the connected account rather than changing the main channel’s profile.
Open Cloudbot settings
Sign in to the Streamlabs account that manages your channel tools, then open the Cloudbot dashboard and select its Settings tab. Streamlabs’ account may need Cloudbot enabled, and its setup instructions indicate that an account can be added through Account Settings if required. The exact navigation labels can change, so use the current Cloudbot dashboard and Streamlabs’ own instructions if the layout differs from what you see here.
Before changing the connection, check whether Cloudbot is enabled for the correct channel. If you manage more than one channel, make sure the dashboard context is the channel where you want the bot to appear. A correct bot account linked in the wrong channel context will not achieve the result you expect.
In the settings area, find the account connection flow. The guide describes using the “Click here to add” option to connect an account to Twitch. The wording and order may vary as Streamlabs updates its interface, but the important point is to initiate the connection from Cloudbot’s settings, rather than assuming that signing in to Streamlabs alone attaches the bot identity.
Pause before opening the platform authorisation page if more than one platform account is signed in. The next step is where the common mistake occurs: a platform can use an existing login session and present the primary account automatically. Opening a new tab does not necessarily create a clean sign-in state.
Connect and authorise the bot account
Start the connection from Cloudbot settings and follow the platform authorisation flow. When the authorisation page appears, inspect the account name or profile shown before approving access. Confirm that it is the separate bot account you chose, not your personal or primary channel account.
Streamlabs specifically warns that Twitch may default to the primary account. If Twitch shows the wrong account, use its “not you?” option to switch accounts, sign in as the bot account, and then continue. Do not approve access first and assume the displayed identity will be changed afterwards. Authorisation attaches the account that is actually active in that flow.
Once the platform confirms the connection, return to Cloudbot and check the connected account information. If it still shows the primary account, stop and correct the connection rather than testing under the wrong identity. Depending on the available controls, disconnect the incorrect account and repeat the authorisation with the bot account explicitly signed in. Avoid repeatedly approving prompts without checking which account is being used.
Test in the channel where you intend to use Cloudbot. Ask a moderator or trusted viewer to check the bot’s visible name and whether it responds to a simple command. If you are managing the stream as well as the bot, make the test outside a busy broadcast where possible, so you can separate a naming or permissions issue from a live production problem. For a continuous channel, a short checklist such as the one in daily tasks for content creators can help you record which account is connected and what you tested.
If the bot is present but does not respond, do not immediately change accounts again. Check that Cloudbot is on and that the bot has the required channel permissions. Streamlabs’ troubleshooting guidance says to mod the selected custom bot name when using the custom-name feature. That permission applies to the bot identity you selected, not the channel owner’s account.
Set up the bot for YouTube
Streamlabs’ name-customisation guide is written around Twitch’s connection flow, but it says the same steps can be followed for YouTube. The general sequence remains: prepare a separate account, open Cloudbot settings, initiate the platform connection, and authorise the intended bot account. Expect YouTube’s own authorisation screens and account selection to differ from Twitch’s, and read each screen rather than relying on the exact Twitch button names.
A Google account can have access to more than one YouTube channel, so check the selected channel identity carefully if the authorisation flow offers a choice. The account displayed in a Google sign-in prompt and the YouTube channel selected for an action are not always the same thing. Confirm the intended channel and bot identity before approving permissions.
Streamlabs lists YouTube among Cloudbot’s supported platforms on its Cloudbot product page, alongside Twitch and Kick. That platform list is not the same as a step-by-step custom-name guide for every platform. The reviewed naming guide covers Twitch and YouTube, while it does not establish that the same custom-name procedure works on Kick. If you are setting this up on Kick, check the latest official Streamlabs documentation before assuming the YouTube or Twitch steps apply.
For a YouTube live channel, keep your bot setup separate from the work of keeping the broadcast itself running. Cloudbot’s account connection does not start or maintain a video broadcast. If you are preparing a prerecorded always-on stream, the guide to starting a 24/7 prerecorded YouTube live channel in India covers the distinct streaming workflow. Treat the bot as one channel tool, not as a substitute for checking the stream, its permissions, or the content being broadcast.
What requires Ultra
Streamlabs distinguishes between Cloudbot and custom naming. Its product page describes Cloudbot as a free cloud-based chatbot and says Ultra subscribers can customise its name so that it differs from the default Streamlabs name. In other words, Cloudbot’s basic availability does not mean custom naming is included at no cost. If you want a bot identity based on a connected account’s username, plan for the Ultra feature and verify the current terms on Streamlabs’ own pages.
This distinction avoids two common misunderstandings. First, connecting a separate account is the mechanism behind the displayed identity; it is not evidence that the custom-name feature is free. Second, having access to Cloudbot’s other listed features does not itself enable the custom-name capability. Streamlabs identifies custom naming with Ultra, so check whether your account has the required subscription access before spending time troubleshooting a feature that is not enabled.
The current product and support pages are the right places to verify feature availability and subscription details, since plans can change. No price is needed to understand the setup, and this guide does not state one. You can compare the current Streamlabs terms directly on its Cloudbot page and the official name-customisation instructions.
If you are deciding whether to use the feature, weigh the visible benefit against the subscription requirement and the work of maintaining a separate account. A distinct bot identity may make messages easier to recognise in a busy chat, but it does not improve channel permissions by itself and it does not guarantee that the bot will respond. You still need to enable the bot, authorise the right account and grant the necessary role in the channel.
Check the connection and recover from a naming problem
If Cloudbot still shows the default name after you connect an account, verify the account shown in Cloudbot settings and check that custom naming is available to your account. The first question is not whether you have typed a name correctly; it is whether the intended bot account is actually connected and whether the Ultra feature is available. Correct those two conditions before changing unrelated channel settings.
If the bot uses the wrong identity, review the platform session used during authorisation. Sign out of the wrong account or use the platform’s account-switching option, then repeat the connection and approve it as the separate bot account. When prompted, pay attention to both the account and channel identity. Keeping a brief note of which account is the bot can prevent the same mix-up during later maintenance.
If the bot stops responding after a name change, Streamlabs recommends turning Cloudbot off, relogging, and turning it back on. Then confirm that the custom bot name has moderator permissions in the channel. The troubleshooting guidance is on Streamlabs’ Cloudbot common problems and solutions page. Follow the current official directions if the interface or available controls have changed.
Separate symptoms rather than resetting everything at once. A bot that appears under the wrong name points first to account selection; a bot that has the correct name but cannot act points to whether it is on and has permission; a bot that worked before a change may need the off, relog and on sequence Streamlabs suggests. This keeps you from changing the channel owner’s account or rebuilding a connection that was already correct.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
Can I change the Cloudbot name without creating a separate account?
The displayed name comes from the account connected as the bot, so a distinct identity requires connecting an account with the username you want to use. Streamlabs recommends a separate bot account rather than using your personal account. Custom naming is an Ultra feature, not a free Cloudbot capability.
Why does Twitch show my primary account during authorisation?
Twitch may use the account already signed in to the browser, which can be your primary account. Use the account-switching or “not you?” option and sign in as the separate bot account before approving access. Check the account name on the authorisation screen before you continue.
Does the same custom-name setup work on YouTube and Kick?
Streamlabs says the same steps can be followed for YouTube, though the sign-in and channel selection screens differ from Twitch. Streamlabs lists Kick as a supported Cloudbot platform, but its reviewed custom-name guide does not document the procedure for Kick. Check current Streamlabs documentation before applying the workflow there.
What should I do if the bot stops responding after I rename it?
Check that Cloudbot is on and that the selected custom bot identity has moderator permissions in the channel. Streamlabs suggests turning Cloudbot off, relogging, and turning it back on if it stopped responding after a name change. If the name itself is wrong, recheck which account was connected.