Discord Error Code 2013 appears when your camera feed reaches Discord at an unusually low frame rate. Discord’s own error-code page ties this message to hardware struggling to process the video feed, and it lists separate network-heavy stream errors for packet loss, poor connection, and low stream quality. Read it as a camera-path problem first, not as a vague warning. [✅Source-1]
Table of Contents
Start with the shortest path: make sure Discord is using the right camera, close any other app that may be holding the webcam, test Discord once with Hardware Acceleration enabled, then test again with it disabled if the feed still crawls. Fast to check. Often enough.
- Desktop app only fails: focus on Discord settings and client isolation.
- Browser and desktop both fail: move to OS permissions, drivers, and camera conflicts.
- Issue gets worse in a dim room: suspect a source frame-rate drop, not only the app itself.
- Issue appears while screen sharing too: treat system load as part of the problem.
What Error Code 2013 Usually Means
Error Code 2013 is best treated as a capture-side warning. Discord can see a camera, but the feed reaches the app too slowly to stay usable. That points you toward camera selection, local processing, permissions, background conflicts, and frame-rate drops at the source. If you also check other Discord error codes, keep 2013 in its own bucket: it is usually not the same class of problem as viewer timeouts or packet-loss alerts.
| What You Notice | Most Likely Path | What to Do Next |
|---|---|---|
| The camera turns on, then looks choppy right away | Local processing or camera-path overload | Toggle Hardware Acceleration, close other camera apps, test the camera outside Discord |
| The browser version works, but the desktop app does not | Client-specific setting or app-side conflict | Try the web app or PTB, then review Discord camera settings |
| The feed drops hardest in low light | Source frame rate falls before Discord encodes it | Add light, reduce load, avoid stacking video tasks at the same time |
| No app can hold a stable camera feed | OS permission, driver, or hardware issue | Check privacy access, update the driver, restart the system |
Work Through the Fix in This Order
- Select the correct camera inside Discord.
- Quit every other camera app before reopening Discord.
- Test Hardware Acceleration one way, then the other; do not assume one state fits every setup.
- Check the feed in another app such as the native Camera app on your system.
- Restart Discord fully, not just minimize and reopen the window.
- Review OS camera permissions for desktop apps and browsers.
- Update the camera driver if the problem appears outside Discord too.
- Use the web app as a clean test; if it works there, the camera itself is often fine.
- Reduce parallel video work such as screen share, recording, filters, and many heavy tabs at once.
Discord Settings That Matter
Discord’s current voice and video help article tells you to check the selected camera device, test the camera in another application, and make sure both Discord and any webcam software are up to date. If you use an external webcam, reconnecting it or moving it to another port is also worth doing before you touch deeper fixes. [✅Source-2]
Discord’s webcam-detection article adds another useful diagnostic move: turn Hardware Acceleration off if the camera still misbehaves, then test Discord PTB or the Discord web app. This is why a methodical toggle matters. One setup improves when acceleration is on; another settles down when it is off. [✅Source-3]
Do not toggle five settings at once. Change one thing, join a call, watch the feed for half a minute, then decide. Clean testing beats random testing.
Windows Checks That Solve a Lot of Cases
On Windows, a slow or unstable Discord camera often traces back to camera access or another app holding the device. Microsoft’s support steps tell you to turn on Camera access, allow desktop apps to use the camera, close background apps that are using it through Task Manager, restart the PC, and also check whether antivirus or third-party security software is blocking camera access. That stack matters more than many short articles admit. [✅Source-4]
Update the Driver Without Guessing
If the camera also stutters outside Discord, update the driver the plain way: open Device Manager, expand the camera category, right-click the camera, choose Update driver, and let Windows search automatically. If you already downloaded a vendor driver, Microsoft also documents the manual browse path from the same window. [✅Source-5]
If Discord Works in the Browser but Not on Desktop
That result is useful. It points away from the webcam itself and toward the desktop client path. When you test Discord in Chrome, make sure the site is actually allowed to use the camera and that the default camera in Chrome’s site settings matches the device you want. If camera access is blocked there, the web test tells you very little. If access is allowed and the browser feed stays smooth, the desktop app becomes the main suspect. [✅Source-6]
Why a Working Camera Can Still Trigger Error 2013
Strange as it sounds, a camera can be working and still send Discord a feed that is too slow. The W3C Media Capture and Streams specification notes that a source may switch to a lower frame rate in low light, and that media can continue flowing even when constraints are no longer fully met. In plain terms: a dim room, auto-exposure slowdown, or rising system pressure can drag a healthy webcam below the cadence Discord wants. [✅Source-7]
- Add more light before you assume the webcam is faulty.
- Close heavy background tasks if the camera becomes jerky only during calls.
- Avoid stacking video work such as camera + screen share + recording + live filters on older hardware.
- Re-test after a restart if the slowdown appeared suddenly after a long session.
Mac Checks That Matter
On a Mac, Apple’s support flow is very direct: update macOS, check Screen Time restrictions if they are enabled, then open Privacy & Security > Camera and make sure the app you want can use the camera. Apple also notes that some apps need to be quit and reopened after permission changes. Clean, simple, and often enough. [✅Source-8]
Load, Frame Rate, and Headroom
Discord publishes a useful frame-rate reference on the streaming side: all users can stream up to 720p at 30fps, while Nitro and Nitro Classic can go up to 4K at 60fps. Even though Error 2013 is about camera input rather than Go Live output, the lesson is the same: every jump in resolution and frame rate asks more from the video path. On a tighter system, headroom disappears fast. [✅Source-9]
| Setup Pattern | Risk Level for Error 2013 | Smarter Move |
|---|---|---|
| Camera only, bright room, light system load | Lower | Keep the setup simple and stable |
| Camera plus screen share on a mid-range laptop | Medium | Cut extra tasks, close heavy tabs, test one video feature at a time |
| Camera, screen share, recording, filters, and many background apps | Higher | Remove parallel video work before changing deeper settings |
| Dim room with auto-exposure working hard | Higher | Improve lighting first, then retest frame stability |
FAQ
What does Discord Error Code 2013 actually mean?
Error Code 2013 means Discord is receiving a camera feed with a frame rate that is too low for stable video use. The camera may still appear, yet the motion cadence drops far enough that Discord flags it.
Should I turn Hardware Acceleration on or off?
Start with the setting that matches the current 2013 fix path, then test the opposite state if the result does not improve. Different camera, driver, and GPU combinations behave differently. Controlled testing works better than assumptions.
Why does the camera work in another app but fail in Discord?
A camera can look normal in a preview app and still send Discord a slow feed. That usually points to a Discord-side setting, a permission difference, extra video load, or a frame-rate drop that shows up only during real-time calls.
Can low light really cause this error?
Yes. In a darker room, the camera may lower its effective frame rate while trying to keep exposure usable. Motion then looks choppy, and Discord may read that as a low-frame-rate camera feed.
Does the Discord web app help diagnose the problem?
Very often, yes. If the browser version works smoothly after camera permission is granted, the webcam itself is usually not the first place to blame. The desktop client path becomes the more likely target.
Do I need a new webcam?
Usually no. Most cases improve after camera access checks, client isolation, driver updates, removing app conflicts, or lowering overall video load. Replace hardware only after those steps fail across multiple apps.