# Get MCEBuddy to use NVidia GPU instead of Intel Integrated **URL:** \ **Category:** Hardware Encoding\ **Created:** [January 1, 2019, 6:41pm UTC](https://discussion.mcebuddy2x.com/t/get-mcebuddy-to-use-nvidia-gpu-instead-of-intel-integrated/2495 "2019-01-01T18:41:35Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![RBoy](https://discussion.mcebuddy2x.com/letter_avatar_proxy/v4/letter/r/2bfe46/32.png) [@RBoy](https://discussion.mcebuddy2x.com/u/RBoy)\ **Post date:** [January 1, 2019, 8:17pm UTC](https://discussion.mcebuddy2x.com/t/get-mcebuddy-to-use-nvidia-gpu-instead-of-intel-integrated/2495/2 "2019-01-01T20:17:50Z")
Handbrake uses Intel QuickSync and FFMpeg uses NVidia acceleration. If you’re using a profile that uses both ffmpeg and handbrake, MCEBuddy will check which hardware encoding capabilities exist and will automatically use the hardware accelerated encoder first. So if your profile has both ffmpeg and handbrake, it will test to see if NVidia acceleration is supported and then it will use ffmpeg first. Most profiles have both ffmpeg and handbrake so it should pick it automatically if acceleration is working. The log files will give you more information about what’s going on. More details here: > [@GPU/Hardware Encoding/Acceleration FAQs](https://discussion.mcebuddy2x.com/t/gpu-hardware-encoding-acceleration-faqs/63): > > This topic is a compilation of the FAQs related to GPU and Hardware encoding 1. What platforms and devices are supported for GPU encoding MCEBuddy supports Intel (QuickSync), NVidia (NVENC/CUDA) and AMD (VCN/VCE/AMF) which are used for decoding and encoding H.264, H.265/HEVC and AV1. See FAQ 2 for driver requirements To use Intel QuickSync H.264 hardware encoders, Intel Sandy Bridge (1st Generation Core) or newer chipsets H.265 hardware encoders, Intel Broadwell (4th Generation Core) … --- _[View the full topic](https://discussion.mcebuddy2x.com/t/get-mcebuddy-to-use-nvidia-gpu-instead-of-intel-integrated/2495)._