Live3D VTuber Maker tracks and displays an avatar; despite its name, it is not an avatar-creation tool. You can select an avatar, calibrate its face tracking and prepare a Streamlabs Desktop scene, but the available Streamlabs Spout2 guide does not list VTuber Maker as a supported sender.
That leaves one practical question to resolve on your own installation: how the avatar image can be brought into the scene without also showing the app window or an unwanted background. Treat capture as a test, not a promised integration. First establish that tracking works in Live3D, then check the current app’s output options and preview any candidate source in Streamlabs before going live.
Understand Live3D VTuber Maker’s role
Streamlabs describes Live3D as a VTuber tool suite and VTuber Maker as face-tracking software. Its overview explains that the app displays and tracks an avatar; the word “Maker” does not mean that it creates the avatar model. You need an avatar to select or otherwise make available to the app before you can test tracking. See Streamlabs’ Live3D overview for the feature description, while bearing in mind that it is dated and current onboarding may differ.
It helps to separate three jobs. The avatar is the model you want viewers to see. VTuber Maker uses camera input to animate or pose that model. Streamlabs Desktop arranges sources, audio and overlays into a scene for broadcast or recording. A working result depends on each handoff, and a successful preview inside VTuber Maker proves only that the first two jobs are working; it does not prove that Streamlabs can capture the avatar cleanly.
This distinction also keeps troubleshooting manageable. If the avatar does not react to your face, investigate Live3D’s camera selection, permissions and calibration. If it animates in Live3D but does not appear as an avatar-only element in Streamlabs, investigate the output route and capture source instead. Do not change several things at once: you want to know which part failed.
If you are new to scenes and sources, think of the avatar as one visual layer among others, rather than as the whole broadcast. Streamlabs can put camera, graphics and other inputs into a scene, but the fact that a source category exists does not establish that it captures a particular app’s output with transparency. The section on capture choices below keeps that distinction explicit.
Choose an avatar and camera
Open the current VTuber Maker app and follow its current sign-in and setup prompts. Streamlabs’ older overview mentions account creation and email verification, but those details may have changed; use the instructions shown by the app rather than relying on an old walkthrough for the exact onboarding sequence. Choose an avatar you are entitled to use and can identify clearly in the app preview. The aim at this stage is simply to confirm that the model loads and can be animated.
Choose the camera that you actually plan to use, then check that the operating system and VTuber Maker can access it. If another app is using the camera, close it or release the camera before testing. Frame your face in consistent lighting, with your head visible and the camera steady. These are practical checks, not published Live3D hardware requirements: the referenced overview does not establish a required resolution, frame rate or camera model.
The camera is for tracking, not necessarily the picture that should appear in your final scene. If your goal is a virtual character over a game, presentation or background, you may want Streamlabs to show only the avatar, not a webcam rectangle or the entire VTuber Maker interface. Do not assume the webcam source in Streamlabs is equivalent to the tracked avatar output. It is a camera image unless some separate, verified route provides the animated model.
Before you build a complicated scene, make a short checklist: the avatar is visible in VTuber Maker, the correct camera is selected, and the camera preview responds when you move. Keep the intended background in mind too. A room or background selected in VTuber Maker may be part of what the app displays, but the available documentation does not say whether that background can be excluded on output. Verify that separately if transparency matters.
Calibrate face tracking
Streamlabs’ Live3D overview shows a webcam preview and red indicators for face tracking, and says to use the camera icon for calibration. In the current app, find that camera control and follow the on-screen calibration process. The indicators give you a useful first check that the software sees facial movement; they do not certify that every expression or head angle will be represented as you expect.
Sit where you expect to sit while streaming and look towards the camera. Make a few natural movements, such as turning slightly, blinking or changing expression, and observe the avatar. If tracking is erratic, check the selected camera and the camera’s view before changing unrelated Streamlabs settings. Improve the lighting or adjust your position if your face is obscured, then calibrate again using the app’s current controls.
Do not chase a perfect animation before confirming a stable basic pose. A camera preview that freezes, switches devices or loses your face can make an otherwise sound scene look broken. Once movement is consistent in VTuber Maker, note the app state and leave it running while you open Streamlabs. This creates a clean baseline for the capture test.
If the avatar looks fine in the Live3D preview but its motion later seems delayed or jerky in a Streamlabs capture, separate tracking from capture. Compare the app preview with the Streamlabs preview under the same movement. The published materials cited here do not provide a Live3D-specific performance diagnosis or recommended camera settings, so avoid treating a particular setting as an official fix. Confirm that your computer can run both applications comfortably and close unnecessary camera or graphics applications during the test.
Prepare the Streamlabs Desktop scene
Open Streamlabs Desktop and create a scene for the avatar test rather than modifying a scene you rely on. Start with a plain background and only the sources needed for the test. Streamlabs’ Desktop getting-started guide covers the general application setup, including camera and microphone inputs and the available capture-source categories. It does not establish a Live3D-specific capture route.
Give the test scene a name you will recognise, then add sources one at a time. If you are also configuring voice audio, check it independently from the avatar image: a moving avatar does not prove that the microphone is routed correctly. Keep the test canvas uncomplicated so that a missing source, wrong crop or duplicate image is easy to notice. Once the visual route is proven, you can add overlays and other scene elements.
Streamlabs documents broad categories such as Window Capture, Display Capture, Game Capture and Screen Capture. These can help test whether some visible output from VTuber Maker is available to the scene. They are general capture features, not confirmation that Live3D will provide a clean avatar-only image or preserve transparency. A window capture may show the application interface; a display or screen capture may include other desktop content. Inspect the result rather than assuming what the source will include.
Keep your broadcast private or use a recording/preview workflow while testing. Check the framing, background and any accidental desktop details before sending the scene to viewers. For a wider guide to previewing a live setup without making it public, see how to test a YouTube radio livestream privately. This is useful even when the scene is intended for VTubing: the point is to verify sources and audio before an audience can see them.
Check documented Spout2 sender support
Spout2 is a way for some applications to pass a visual feed between Windows applications, and Streamlabs has a specific Spout2 guide. That guide names VTube Studio and VSeeFace. It does not list Live3D VTuber Maker as a supported sender. Read the Streamlabs Spout2 instructions as instructions for the named apps, not as evidence that the same steps work with Live3D.
This is the important boundary in the setup. Do not select a Spout2 source in Streamlabs and conclude that Live3D is compatible merely because another VTuber app works that way. The available documentation does not resolve whether the current VTuber Maker version provides a Spout2 sender or a virtual camera. Check the current Live3D app’s own output or integration options and current support material. If neither identifies a route, ask Live3D support rather than promising a method based on a similar app.
The distinction matters because a capture route has several properties beyond whether something appears. You need to know whether it gives Streamlabs only the avatar, whether it includes the app window or background, whether it retains transparency, and whether extra setup is required. The cited Spout2 guide establishes an approach for its named senders, but the evidence here does not establish those properties for VTuber Maker. A visible rectangle can be a successful capture in the narrow sense while still being unsuitable for your scene.
| Route to investigate | What the cited documentation establishes | What you still need to test |
|---|---|---|
| Spout2 | Streamlabs documents a procedure for VTube Studio and VSeeFace, not VTuber Maker. | Whether the current Live3D app offers a compatible sender; do not assume it does. |
| Window Capture | Streamlabs offers this general source category. | Whether the Live3D window is selectable and whether the result includes interface elements or an unwanted background. |
| Display or Screen Capture | Streamlabs offers general display/screen capture categories. | Whether the captured desktop can be cropped safely and whether it is practical for the scene. |
| Game Capture | Streamlabs lists this general capture category, and its Spout2 guide mentions it in troubleshooting for the named apps. | Whether it captures VTuber Maker at all; no Live3D result is documented here. |
| Camera source | Streamlabs supports adding a camera, and Live3D uses a webcam preview for face tracking. | Whether a separate virtual camera exists in the current Live3D app; an ordinary webcam source is not the animated avatar. |
These are investigation paths, not recommendations that promise a clean feed. If Live3D documents a virtual camera or another output in your current version, follow that product’s instructions and test it in a blank scene. If it does not, a general capture source might still show the app, but decide whether the resulting frame is acceptable before designing a full broadcast around it.
Verify the avatar feed in the scene
With Live3D open and the avatar moving, add only the candidate source you are testing in Streamlabs. Check that the source updates when you move, that the correct window or output is selected, and that the visible result is the content you intend viewers to see. If the app appears twice, or the avatar is buried under another source, inspect the scene’s source list and visibility order. Do not interpret a blank source as proof that the avatar itself is broken when it still animates in VTuber Maker.
For the documented Spout2 apps, Streamlabs advises checking that both applications are running and relaunching if the sender is missing. Its guide also discusses switching auto Game Capture to Specific Window when an avatar appears twice. Those are troubleshooting notes for the Spout2 workflow and named applications, not Live3D-specific fixes. You may use the general diagnostic idea—check that both programs are open and the intended source is selected—but do not claim that these steps establish Live3D support.
Inspect the edges and background carefully. If the capture includes a desktop, controls, menus or a room you did not intend to show, it is not an avatar-only result. If transparency is required, confirm that the chosen output actually supplies transparency in the Streamlabs preview; do not infer it from a dark or matching-colour background. If your design uses a solid background intentionally, decide whether the whole captured rectangle works visually before adding overlays.
Next, test scene behaviour over time rather than relying on a single still preview. Move your head, look away briefly and return to the expected position; confirm the avatar remains visible and tracking recovers. Check voice audio and any other inputs separately. If the route is unstable, document which source and app state you tested, then consult the current product help pages. Avoid going live until you can explain what the source contains and reproduce the result after reopening the applications.
If you later turn the scene into a continuous YouTube programme, treat that as a separate broadcast design problem. An animated character in a scene is not the same as a ready-made 24/7 programme file. For example, how looping prerecorded videos on YouTube Live works explains the different considerations when the material is a repeating video rather than a live, tracked avatar. For a planned sequence of animated scenes, a TV-schedule approach for a 24/7 animated channel may help with programming, but it does not solve the Live3D capture question.
Choose a workflow that matches the evidence
If current Live3D documentation gives you an output specifically intended for another application, test that first because it is the clearest route to validate. If all you can confirm is that Streamlabs can capture a window or screen, decide whether a full-window image is acceptable for your layout. If it is not, do not build the entire show around an assumed crop or transparency behaviour. The missing information is a real constraint, not a reason to improvise a guarantee.
Make a brief record of the app versions, source type and result, especially if you plan to use the scene repeatedly. This is not a substitute for official support, but it makes it easier to reproduce a working configuration or ask a precise question: “Does this version of VTuber Maker expose a virtual camera or Spout2 output, and what output is supported in Streamlabs Desktop?” Ask about the output format and transparency as well as whether the app is visible.
Once a capture path is confirmed, save the scene and reopen both applications to repeat the check. A setup that worked once may depend on a selected window, device permission or app state. For a long-running broadcast, the computer and applications also need to remain available, so distinguish a scene that works during a short test from a continuous operating plan. If you are considering a recorded loop instead, the workflow for managing media in a video editor is relevant to preparing source files, but it does not animate Live3D or establish a capture integration.
If you want to run the finished scene continuously, compare the operating approach with your actual requirements: whether the avatar needs to react live, whether a prepared recording is enough, and whether you can keep the tracking and broadcast applications running. StreamNeo turns an uploaded video into a 24/7 YouTube live stream, which removes the need to leave your own computer running for a prerecorded file; it does not provide live VTuber tracking or solve the Live3D-to-Streamlabs handoff. Keep those workflows distinct when deciding what to test.
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
Does Live3D VTuber Maker create an avatar?
No. Streamlabs describes VTuber Maker as software for tracking and displaying avatars, despite the app’s name. Select an avatar that is available to you, then use the app to animate it with face tracking.
Does Streamlabs document VTuber Maker as a Spout2 sender?
The cited Streamlabs Spout2 guide names VTube Studio and VSeeFace, not Live3D VTuber Maker. Check Live3D’s current documentation or app output options for a supported route; do not assume the other apps’ instructions apply.
Can I use Window Capture to show the avatar?
Streamlabs offers Window Capture as a general source, but the available documentation does not confirm that it produces an avatar-only or transparent Live3D feed. Test the current app and inspect whether the result includes its interface or background before relying on it.
What should I check before going live?
Confirm that face tracking works in VTuber Maker, then verify the candidate source, framing, background and audio in a Streamlabs preview. Repeat the test after reopening both apps and use a private test workflow if you need to check the complete broadcast.