---
description: Windows
---

# Optimizing Live Streaming Performance

When live streaming on a low-spec PC, there is a risk of app crashes, stuttering, or frequent screen interruptions. To ensure stable transmission, consider the following tips when using the app on a low-spec PC:

1. Check if other programs are running while transmitting.
2. Verify whether your PC meets the required specifications.
3. Adjust PRISM app settings, including sources, scenes, and encoder configurations.





***



## Checking other programs

Running multiple programs during live broadcasting can significantly impact CPU, GPU, and memory usage, reducing overall system performance.

To optimize performance, close resource-intensive programs using the **Task Manager** before starting your broadcast.



***



## ​Checking PC specification <a href="#id-94cc" id="id-94cc"></a>

When launching PRISM Live Studio, the app inspects whether your PC meets the required specifications. If you are using a low-spec PC, a notification message will appear in the lower right corner of the screen.

<figure><img src="https://miro.medium.com/v2/resize:fit:1400/1*JasAXfz3o1AUZd7LHL3pLw.png" alt=""><figcaption></figcaption></figure>



For recommended system requirements for stable transmission, check the image below or visit [Help](https://prismlive.com/en_us/faq/faq.html?app=pcapp) **> Install and Start > System requirements**.



<figure><img src="https://miro.medium.com/v2/resize:fit:1400/1*6xJ_CSGlqCOYHB3j7Q-ggw.png" alt=""><figcaption><p>Minimum Specifications</p></figcaption></figure>



<figure><img src="https://miro.medium.com/v2/resize:fit:1400/1*q6XQuPcT3uTg67GZ9kPCHQ.png" alt=""><figcaption><p>Recommended specifications for general broadcasting</p></figcaption></figure>



<figure><img src="https://miro.medium.com/v2/resize:fit:1400/1*rmArGIhr3QzfCx3imSnEMg.png" alt=""><figcaption><p>Recommended specifications for gaming broadcasting</p></figcaption></figure>





***



## Checking PRISM app settings

Even if your PC meets the required specifications, transmission issues may still occur depending on the number of sources, scenes, and other settings. If you experience transmission delays, consider adjusting the settings as outlined in the table below. The table details the impact of different sources and settings on CPU and GPU usage.

<figure><img src="https://1019928184-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlISC5rfB4Hnmbsjf8phq%2Fuploads%2FzJiRVpHXXRLcUeDr4fEG%2Fapp_setting_summary.jpg?alt=media&#x26;token=b6c23de6-11f2-49c9-a674-665ba8c2bfe3" alt=""><figcaption><p>Item table for CPU/GPU impact on PRISM app</p></figcaption></figure>





As shown, no specific recommendations are needed when the performance impact is **low**. However, this does not mean you can add an unlimited number of “low” impact items, as excessive additions can still result in **high** performance consumption. To optimize settings:

* Open **Task Manager** and monitor CPU/GPU usage while adding sources one by one.
* Adjust settings accordingly to prevent performance degradation.





### Source

For detailed instructions on using each source, refer to the [sources](../../sources "mention") pages, or visit [**Help** ](https://prismlive.com/en_us/faq/faq.html?app=pcapp)**> Prepare Scene and Source > Add Source**.

<figure><img src="https://1019928184-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlISC5rfB4Hnmbsjf8phq%2Fuploads%2FXIqRBiI5uKWIKz44qveg%2Fsourcelist.png?alt=media&#x26;token=e143640a-02c9-4bb6-b91a-4e232f2d3a39" alt=""><figcaption><p>The Source list.</p></figcaption></figure>





#### Video Capture Device <a href="#e6e7" id="e6e7"></a>

A **Video Capture Device** source allows real-time transmission using a connected camera. The higher the resolution and FPS, the more GPU resources are consumed. Additionally, adding multiple video capture sources will increase both CPU and GPU load.

We recommend the following settings:

* **Match the device resolution to the output resolution.**\
  If the output resolution is 1080p but the camera resolution is set to 4K, the captured video will be downscaled to 1080p, leading to unnecessary resource consumption.
* **Adjust FPS settings based on PC performance.**\
  If your PC has limited processing power, set FPS to 30 or lower.
* **Enable the ‘Disable if invisible’ option in the properties window of unused sources.**\
  This prevents hidden sources from consuming unnecessary CPU/GPU resources.





#### Display Capture <a href="#id-2ec3" id="id-2ec3"></a>

A **Display Capture** source allows real-time screen sharing. The performance impact varies based on the capture method:

• **Windows 10 (1903 and later)** capture uses less GPU but higher CPU.

• **DXGI Desktop Duplication** capture consumes less CPU but requires moderate GPU usage.

For optimal performance, set the capture method to **DXGI capture** in the **source properties** window.

<figure><img src="https://1019928184-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlISC5rfB4Hnmbsjf8phq%2Fuploads%2F6TqrEOesNELtSj43fTEQ%2Fdxgi.png?alt=media&#x26;token=1e4b16e0-e941-44d8-b320-e13f4139d81a" alt=""><figcaption><p>Set the capture method to <strong>DXGI Desktop Duplication</strong> capture.</p></figcaption></figure>





#### Display Capture (Part) <a href="#e590" id="e590"></a>

The **Display Capture (Part)** source allows you to capture and share a specific portion of your monitor in real time. However, performance issues may arise if the PRISM app and the monitor are using different graphics cards. Additionally, higher screen resolutions will result in increased GPU consumption.

We recommend the following:

* **Use Windows 10 or a later version.**
* **Ensure that the PRISM app and the monitor use the same graphics card.**
  * To check which graphics card your monitor is using:&#x20;
    * Right-click on an empty area of the **desktop** > **Display** **Settings** > **Advanced** **Display** > Check **Graphics** **Card Information**.
  * To check which graphics card the PRISM app is using:
    * Right-click on an empty area of the **desktop** > **Display** **Settings** > **Graphics** > Select PRISM app from the list > Click **Options** > Check the **graphics** **card**.
  * For more details on configuring graphics cards, refer to the following page:
    * [configuring-graphics-card-for-prism-app](configuring-graphics-card-for-prism-app "mention")





#### Game Capture <a href="#id-78a9" id="id-78a9"></a>

Adding a Game Capture source allows you to capture a game’s screen and render it in real time within PRISM.

We recommend the following:

* **Disable the ‘SLI/Crossfire Capture Mode (Slow)’ option if you have only one graphics card.**\
  This option is found in the Game Capture source properties window.
*   **Ensure that the game and PRISM app use the same graphics card.**

    To verify and adjust settings:

    * Right-click on an empty area of the desktop > Display Settings > Graphics > Select PRISM app from the list > Click Options > Check the graphics card.
    * For more details on configuring graphics cards, refer to the following page:
      * [configuring-graphics-card-for-prism-app](configuring-graphics-card-for-prism-app "mention")

<figure><img src="https://miro.medium.com/v2/resize:fit:1400/1*xbgziS7jdMGFHgNZPBZhug.png" alt=""><figcaption><p>Disable the <strong>SLI/Crossfire Capture Mode(Slow)</strong> option.</p></figcaption></figure>





#### Window Capture <a href="#id-1717" id="id-1717"></a>

The Window Capture source allows you to capture a specific application window instead of the entire screen.

We recommend the following settings:

* **Set the capture method to ‘Windows Graphics Capture (Windows 10 1903 or later)’.**\
  This option is available in the **Window Capture** source properties window.

<figure><img src="https://miro.medium.com/v2/resize:fit:1400/1*kc1sSoB89DxXHvi3TupZWg.png" alt=""><figcaption><p>Set the capture method to <strong>Windows Graphics Capture (Windows 10 1903 or later).</strong></p></figcaption></figure>





* **Disable the ‘Multi-adapter Compatibility’ option when using BitBlt as the capture method and if you have only one graphics card.**

<figure><img src="https://miro.medium.com/v2/resize:fit:1400/1*MrZMVCJWQeDLmwJmf4CrcQ.png" alt=""><figcaption><p>Disable the <strong>Multi-adapter Compatibility</strong> option.</p></figcaption></figure>





#### Browser <a href="#id-160f" id="id-160f"></a>

The **Browser** source enables you to embed live content from web pages into your broadcast. However, adding multiple browser sources can significantly increase GPU usage, even if the ‘**Use hardware acceleration when available**’ option is disabled.

We recommend the following:

* **Minimize the use of browser sources whenever possible.**
* **Enable the ‘Use hardware acceleration when available’ option.**

<figure><img src="https://miro.medium.com/v2/resize:fit:1400/1*dBbzVjOOWJovm3tp0McDag.png" alt=""><figcaption><p>Enable the <strong>Use hardware acceleration when available</strong> option.</p></figcaption></figure>





#### Media source <a href="#id-3701" id="id-3701"></a>

The Media Source allows you to add and play video or audio files stored on your device. Larger files consume more CPU, and enabling hardware decoding can also increase GPU usage.

We recommend the following:

* **Match the media resolution to the transmission resolution.**\
  For example, if a 2K video is played while the broadcast resolution is set to 1080p, the video will be downscaled during transmission. To avoid unnecessary quality loss, it’s best to convert videos to the correct resolution before adding them to PRISM.
* **Enable the ‘Use hardware decoding when possible’ option in the source properties window.**\
  This setting is particularly useful for large videos when the GPU is more powerful than the CPU.





#### Image <a href="#d180" id="d180"></a>

Image files (JPG, PNG, GIF) added through the Image Source can be used in your broadcast. However, adding many images or using high-resolution files increases CPU/GPU usage.

We recommend the following:

* **Reduce the use of large, high-resolution images.**
* **Pre-compress images to match or stay below the output resolution.**\
  Even if an image is in higher resolution than the broadcast output, it will still be compressed to match the output resolution, potentially causing quality loss.



#### Image Slide Show <a href="#id-7050" id="id-7050"></a>

The Image Slide Show source allows you to create automated or manually controlled slideshows for your broadcast. Adding too many images can increase CPU load when loading the slideshow, while GPU usage may also rise.

We recommend the following:

* **Avoid adding an excessive number of images in the source properties window.**
* **Pre-compress images to match or stay below the output resolution.**
* **Add images before broadcasting or recording rather than during the session.**\
  Adding images during a live broadcast may cause sudden spikes in CPU usage, affecting stream quality.





#### Scene <a href="#id-25e4" id="id-25e4"></a>

Adding a Scene Source allows you to combine existing scenes and sources into a single source. However, using too many scene sources—especially when the exposure method is set to Real-time screen—can increase CPU consumption.

We recommend the following:

* **Limit the number of scene sources used.**
* **Adjust the scene exposure method based on the number of scenes.**\
  When using 10 or more scenes, set the exposure method to **Text** or **Thumbnail** in **Settings > General > Display Method**.

<figure><img src="https://1019928184-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlISC5rfB4Hnmbsjf8phq%2Fuploads%2FE2tAR4jj4hr20JlNd13e%2Fperformance3.jpg?alt=media&#x26;token=183cd862-c8fe-4b64-bc3d-095cc7ed00c6" alt=""><figcaption><p>Set the exposure method to <strong>Text</strong> or <strong>Thumbnail.</strong></p></figcaption></figure>





#### PRISM Lens & PRISM Mobile <a href="#id-26c4" id="id-26c4"></a>

The **PRISM Mobile** source utilizes **PRISM Lens**, which provides features such as **beauty effects** and **virtual backgrounds**. These features can significantly impact GPU and CPU performance, especially when used at higher resolutions or higher FPS settings.

We recommend the following:

* **Use effects sparingly.**\
  Features such as beauty effects and virtual backgrounds are resource-intensive, so use them only when necessary.
* **Match the source resolution to the transmission resolution.**\
  For example, if a 2K video is played while the broadcast resolution is set to 1080p, the video will be downscaled, leading to quality loss. It is recommended to pre-convert the video to match the transmission resolution before adding it to PRISM app.
* **Enable the ‘Hardware’ option for decoding in PRISM Lens settings.**\
  You can find this option in **Settings > General > Decoding Method**.

<figure><img src="https://1019928184-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlISC5rfB4Hnmbsjf8phq%2Fuploads%2FkX9cST09LxV1uYacI3fT%2Fperformance1.jpg?alt=media&#x26;token=ff0aa151-6574-4f56-a981-56b5656353df" alt=""><figcaption><p>Enable the <strong>Hardware</strong> option for decoding in PRISM Lens settings.</p></figcaption></figure>





#### PRISM Sticker <a href="#id-6a46" id="id-6a46"></a>

**PRISM Stickers** allow you to decorate the broadcast screen with various animated stickers. However, loading unused stickers consumes GPU/CPU resources.

We recommend adding stickers before broadcasting or recording, rather than during the session, as used stickers can be loaded with lower performance costs.





#### GIPHY Sticker <a href="#id-99b1" id="id-99b1"></a>

The **GIPHY Sticker** source provides access to a variety of free animated stickers. The performance impact depends on the number of images displayed, the number of frames in each animation, and the window size.

We recommend using a reasonable number of stickers based on your PC’s performance.





#### Music Playlist <a href="#id-653a" id="id-653a"></a>

You can add and play local music files stored on your PC, as well as free music provided by PRISM.

To prevent unnecessary performance issues, it is recommended to avoid using excessively large audio files.





#### Audio Visualizer <a href="#dfac" id="dfac"></a>

The **Audio Visualizer** feature renders real-time visual effects based on audio input, consuming GPU resources.

For optimal performance, we recommend using the default template with the default values in the source properties window.





#### Background Template <a href="#id-9172" id="id-9172"></a>

Background Templates allow you to add motion-based backgrounds to your scene. The MY tab in the source properties window lets you upload your own images for virtual backgrounds.

We recommend the following:

* **Avoid adding large, high-resolution videos.**\
  A 4K video will consume a large amount of CPU and GPU resources. A video smaller than 2K is recommended for smoother performance.





***



### Scene <a href="#id-2116" id="id-2116"></a>

You can view the list of scenes and list of sources in the image below. The scene thumbnail preview allows you to view all sources included in that scene.

<figure><img src="https://1019928184-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlISC5rfB4Hnmbsjf8phq%2Fuploads%2FjXLtUzIvUaYjyc3s4Uwf%2Fperformance2.png?alt=media&#x26;token=f09b7e8b-03bc-4840-bde0-dfa18debd683" alt=""><figcaption><p>You can preview each scene through its thumbnail.</p></figcaption></figure>





#### Scenes <a href="#id-3660" id="id-3660"></a>

The Scenes List displays the currently active scenes. The more scenes you have, the more CPU/GPU resources will be consumed.

We recommend setting up an appropriate number of scenes based on your broadcasting needs.





#### Scene Sets

A **Scene Set** lets you group multiple scenes and sources into one collection, which can then be saved, imported, and exported in PRISM app. However, larger scene sets with many scenes and sources will result in higher CPU/GPU usage.

To optimize performance:

* **Reduce the number of scenes and sources** in your saved scene collection file.

For more information about using Scene Sets, please refer to the following page:

* [managing-scene-sets](../../features/scene/managing-scene-sets "mention")





#### Sources

The Sources List displays all sources added to each scene. The more sources you include, the higher the CPU/GPU consumption.

We recommend the following:

• Limiting the number of sources per scene.

• Removing unnecessary sources from the source list.





#### Scene Thumbnail <a href="#e8e8" id="e8e8"></a>

The Scene Thumbnail feature provides a live preview of all sources included in each scene. Since this function increases CPU and GPU load, we recommend limiting its usage.

To optimize performance:

* **djust the scene exposure method based on the number of scenes.**\
  When using 10 or more scenes, set the exposure method to **Text** or **Thumbnail** in **Settings > General > Display Method**.

<figure><img src="https://1019928184-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlISC5rfB4Hnmbsjf8phq%2Fuploads%2FE2tAR4jj4hr20JlNd13e%2Fperformance3.jpg?alt=media&#x26;token=183cd862-c8fe-4b64-bc3d-095cc7ed00c6" alt=""><figcaption><p>Set the exposure method to <strong>Text</strong> or <strong>Thumbnail.</strong></p></figcaption></figure>





***



### Encoder settings <a href="#id-9f35" id="id-9f35"></a>

PRISM supports various encoder types, including software encoding (x264/AV1) and hardware encoding (NVIDIA/AMD). In Settings, select the **Output** tab and set **Output Mode** to **Advanced**. And in the **Streaming** section, locate the **Video Encoder** option. The exact name may vary depending on your graphics card manufacturer.

<figure><img src="https://1019928184-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlISC5rfB4Hnmbsjf8phq%2Fuploads%2FkMRU0tSQy5OlwOL1W6N7%2Fperformance5.jpg?alt=media&#x26;token=47b6692d-9e58-40e5-a249-c55254c02440" alt=""><figcaption><p>Follow the order indicated on the image to set <strong>Encoder.</strong></p></figcaption></figure>





For x264 or x265 encoding, we recommend adjusting the CPU Usage Preset（higer = less CPU）option to **veryfast**. If you select **veryslow** for this option, it uses a lot of CPU resources. Scroll down to find **CPU Usage Preset** option.

<figure><img src="https://miro.medium.com/v2/resize:fit:1400/1*n4MMBQg1VmvBDGrB5AcfXA.png" alt=""><figcaption><p>Higher presets (e.g., veryslow) consume significantly more CPU resources.</p></figcaption></figure>





***



### Output settings <a href="#b047" id="b047"></a>

For optimal performance, we recommend lowering the broadcast resolution, bitrate, and FPS settings. Higher resolution, bitrate, and FPS settings can put strain on both your PC and network bandwidth.

To adjust these settings, go to **Settings**, select the **Output** tab and set **Output Mode** to **Advanced**. And in the **Streaming** section, scroll down to locate the **Bitrate** option.

You can set resolution and FPS in **Settings > Video** tab.

<figure><img src="https://1019928184-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlISC5rfB4Hnmbsjf8phq%2Fuploads%2F4MbAFr6NiMrqhOQQ7kqW%2Fperformance6.jpg?alt=media&#x26;token=a62012be-8449-46f5-bf0b-56a1d11bb75f" alt=""><figcaption><p>Set Bitrate.</p></figcaption></figure>



<figure><img src="https://1019928184-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlISC5rfB4Hnmbsjf8phq%2Fuploads%2Fnb2ygSl3gmcYSXKXQNtv%2Fperformance4.jpg?alt=media&#x26;token=02385ef7-ed5b-4d81-b81c-00e74f6a790e" alt=""><figcaption><p>Set resolution and fps.</p></figcaption></figure>





If you are using a dedicated graphics card, we recommend selecting Hardware (NVIDIA/AMD) in the encoder options. To adjust these settings, go to **Settings**, select the **Output** tab and set **Output Mode** to **Advanced**. And in the **Streaming** section, locate the **Video Encoder** option. The exact name may vary depending on your graphics card manufacturer.

<figure><img src="https://1019928184-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlISC5rfB4Hnmbsjf8phq%2Fuploads%2FkMRU0tSQy5OlwOL1W6N7%2Fperformance5.jpg?alt=media&#x26;token=47b6692d-9e58-40e5-a249-c55254c02440" alt=""><figcaption><p>Select Hardware (NVIDIA/AMD) encoder when using a dedicated graphics card.</p></figcaption></figure>





***



### Others <a href="#b047" id="b047"></a>

#### Beauty Effect in PRISM Lens <a href="#id-6a48" id="id-6a48"></a>

The **Beauty Effect** feature enhances facial appearance by smoothing skin and adjusting facial features.

Since this feature is GPU-intensive, we do not recommend enabling it on low-spec PCs.



#### Virtual Background in PRISM Lens <a href="#c560" id="c560"></a>

The Virtual Background feature allows you to remove or replace the camera background. This feature mainly relies on GPU resources.

We recommend the following:

* **Avoid using Virtual Backgrounds on multiple lenses simultaneously.**
* **Close the PRISM Lens window after setting the Virtual Background.**\
  The app and the effect will remain active while running in the background.
* **Do not use images larger than 2K when importing backgrounds.**
* **Prefer background blur instead of virtual background images.**\
  Background blur consumes fewer resources than full virtual backgrounds.





<figure><img src="https://miro.medium.com/v2/resize:fit:1400/1*tFAuE8H37EfBawLnBVb91A.png" alt=""><figcaption><p>Prefer background blur instead of virtual background image.</p></figcaption></figure>





#### Drawing mode <a href="#id-7de0" id="id-7de0"></a>

The **Drawing Mode** feature allows users to draw directly onto the broadcast screen. This feature mainly relies on GPU resources.

We recommend the following:

* **Testing performance on your PC before prolonged use.**
* **Using for simple figures rather than complex drawings.**

For more information about using Drawing mode, please refer to the following page:

* [live-drawing-on-screen](../../features/others/live-drawing-on-screen "mention")



#### Multiview <a href="#id-9005" id="id-9005"></a>

The **Multiview** feature allows you to view multiple scenes, including the EDIT screen, LIVE screen, and scene list, in a single interface. Although this feature not requires large GPU processing, we recommend minimizing the use of Multiview on low-spec PC.

To use Multiview, navigate the **Menu > View > multiview**.

<figure><img src="https://miro.medium.com/v2/resize:fit:1400/1*RUKDeqnZ48WxvIny5lqWWg.png" alt=""><figcaption><p>Navigate the <strong>Menu > View > multiview.</strong></p></figcaption></figure>



<figure><img src="https://1019928184-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlISC5rfB4Hnmbsjf8phq%2Fuploads%2FwbaQBR5dPbWMEz0FDeUu%2Fperformance7.png?alt=media&#x26;token=9075b2cc-142d-4070-af6e-f73f50284661" alt=""><figcaption><p>Multiview example</p></figcaption></figure>





#### Source Projector <a href="#ba58" id="ba58"></a>

The **Source Projector** feature displays the LIVE screen and selected scenes in a separate window. As the number of projected scenes increases, so does GPU consumption. If using a low-spec PC, we recommend minimizing the use of Source Projector.

There are two ways to access Source Projector:

* **Right-click the LIVE screen in Studio Mode.**
* **Right-click a scene in the Scenes tab.**

<figure><img src="https://miro.medium.com/v2/resize:fit:1244/1*IMJzjnczwaxRYl1kMgkzPA.png" alt=""><figcaption><p>Right-click the LIVE screen in <strong>Studio Mode</strong>.</p></figcaption></figure>



<figure><img src="https://miro.medium.com/v2/resize:fit:1046/1*Uj00PJWu65Q0-TfUPxcErQ.png" alt=""><figcaption><p>Right-click a scene in the <strong>Scenes</strong> tab.</p></figcaption></figure>







[..](../../.. "mention"), [..](../.. "mention"), [..](.. "mention"), [](<> "mention")
