Quick answer: In Remote Desktop Connection, go to Show Options > Experience and uncheck Persistent bitmap caching and Font smoothing, then reconnect. If flicker persists, disable hardware acceleration in the app that flickers (browsers are the usual suspects). Those two changes end most RDP screen flickering.
Name the flicker: three common patterns
Not all flicker is the same, and the pattern points at the layer. Pattern one: flicker when scrolling or switching windows. Web pages shimmer as you scroll, or windows tear when dragged. This is the classic bitmap-caching artifact — the client is reusing stale cached screen tiles, and the cache disagrees with the new frame. It is the most common RDP flicker and the easiest to fix.
Pattern two: flicker or black flashes during video or animation. A video plays, then the video area flashes black or freezes while audio continues. This is the video codec path struggling — the server encodes the moving region with the AVC/H.264 codec and something in that encode-decode chain stumbles, often under bandwidth pressure or with an overloaded server-side encoder.
Pattern three: constant shimmer or blinking across the whole desktop. Everything pulses gently, or the entire screen blinks at intervals. This points below RDP at the server's own display stack — a display driver issue, a conflicting screen-capture hook, or an application forcing hardware overlays that do not survive remote rendering.
Watch for thirty seconds and decide which pattern you have. The fixes below are ordered to match: start with the client Experience settings for pattern one, move to encoding and bandwidth for pattern two, and go server-side for pattern three.
Tune the Experience settings
The Experience tab in Remote Desktop Connection controls how much visual fidelity the session attempts — and each option is a potential flicker source. The connection-speed dropdown at the top is a preset: choosing a slower preset disables the eye-candy options below it. For flicker hunting, set the dropdown to a middle preset and then adjust individual checkboxes deliberately.
Persistent bitmap caching is suspect number one for scroll-and-drag flicker. It stores screen tiles on your local disk so they do not need retransmission, but stale tiles cause exactly the shimmering-tearing pattern. Uncheck it. Font smoothing is suspect number two: it renders text with subpixel anti-aliasing tuned for a physical monitor, which can shimmer when the image is compressed and re-rendered remotely — uncheck it and see if text stabilizes. Desktop composition enables the full Aero-style window manager; on an overloaded server it can stutter, so try it off.
Two settings you generally want to keep: Visual styles off is fine (it just flattens the theme), and dropping color depth to 16-bit on the Display tab reduces the data the encoder must push per frame, which helps pattern-two video flicker on slow links. Change one thing at a time and reconnect between changes — stacking five changes at once teaches you nothing about which one worked.
Server-side: display adapter and drivers
When the whole desktop shimmers (pattern three), look at the server's display stack. Open Device Manager on the server and expand Display adapters. On a virtual server you will typically see a basic Microsoft display adapter rather than a real GPU — that is normal. What is not normal is a warning icon on the adapter, or a third-party screen-capture, overlay, or "virtual display" driver that some installed application added. Those hooks intercept frames before RDP encodes them and are a classic source of full-screen blinking.
If a suspect driver is present, disable it in Device Manager and reconnect — do not uninstall blindly, in case a legitimate tool needs it. Also check for applications that install global overlays: game launchers, screen recorders, and some "desktop enhancement" utilities. If the flicker started the same day something like that was installed on the server, you have found your culprit. This is another place where full admin access matters: without it you cannot touch drivers or services.
One more server-side lever: the Remote Desktop Services policies around graphics. In high-load terminal environments, administrators sometimes force the AVC/H.264 codec or restrict it; if video-region flicker (pattern two) appeared after a server change, ask support whether the graphics encoding settings were touched. On a personal hosted server where you are the admin, leaving the defaults is usually correct.
| Flicker pattern | Pipeline stage | Fix to try first |
|---|---|---|
| Shimmer/tearing when scrolling or dragging windows | Client cache | Disable persistent bitmap caching; reconnect |
| Video area flashes black or freezes | Encoder / bandwidth | Lower color depth to 16-bit; reduce server load |
| Whole desktop pulses or blinks steadily | Server display stack | Check Device Manager for bad/hooked display drivers |
| Text shimmers but graphics are fine | Font rendering | Disable font smoothing in Experience settings |
| Flicker only in one application | App rendering | Disable hardware acceleration in that app |
| Flicker starts minutes after connecting | Resource exhaustion | Check server CPU/RAM; close heavy apps |
App-level: hardware acceleration
Browsers are the single biggest source of app-level flicker over RDP. Chrome, Edge, and Firefox all use the GPU for rendering by default, and inside a remote session that GPU path goes through layers that were never designed for it — the result is flickering page content, flashing video, or black rectangles where web content should be. The fix: in the browser's settings, search for "hardware acceleration" and turn "Use hardware acceleration when available" off, then relaunch the browser. This forces software rendering, which travels through RDP cleanly.
The same logic applies to any app with a hardware-acceleration toggle: Discord, Slack, VS Code, media players. If exactly one application flickers while the rest of the desktop is calm, that application's rendering path is the problem, not RDP itself. Toggle its acceleration setting before touching anything session-wide.
Video playback deserves a special mention. If you watch video on the server regularly and it flickers, consider whether the video needs to play on the server at all — streaming it locally in your own browser bypasses the entire remote-encoding path. For the audio side of the same scenario, the audio fix guide covers getting sound to your local speakers.
Stop the flicker: step by step
Work the pipeline from the cheapest fix to the deepest:
- Name the pattern. Scroll-flicker, video flicker, or whole-desktop shimmer — write down which one you see.
- Open Experience settings. Remote Desktop Connection > Show Options > Experience tab.
- Uncheck persistent bitmap caching. This alone fixes most scroll-and-drag flicker. Save and reconnect.
- Uncheck font smoothing. If text shimmers, this is the next most likely cause. Reconnect and check.
- Disable hardware acceleration in the flickering app. Browsers first: settings > hardware acceleration off > relaunch the app (not the session).
- Drop to 16-bit color. Display tab > Colors > High Color (16 bit). Helps video flicker on slow connections.
- Inspect the server's display drivers. Device Manager > Display adapters — disable suspect third-party or virtual display drivers.
- Check server load. Flicker that starts minutes into a session can be CPU/RAM exhaustion — close heavy apps and retest.
If the display is the wrong size as well as flickery, fix the geometry first with the display resolution guide — a session fighting both problems is hard to diagnose. And on mobile clients, where the rendering path is entirely different, the Android and iPhone guides cover the relevant display toggles.
Need an RDP server that just works?
Full admin access, dedicated IP, 24/7 support and a 3-day money-back guarantee on every plan.
3-day money-back guarantee · Dedicated IP on every plan · 24/7 support
RDP Screen Flickering: FAQ
That is usually stale persistent bitmap caching: the client reuses cached screen tiles that no longer match the new frame. Uncheck Persistent bitmap caching on the Experience tab of Remote Desktop Connection, save, and reconnect.
First disable hardware acceleration in the browser or player showing the video, which forces software rendering that travels cleanly over RDP. If it still flickers, drop the session color depth to 16-bit to reduce the encoder's workload.
Font smoothing renders subpixel anti-aliased text tuned for a physical monitor, which can shimmer once compressed for remote display. Turning font smoothing off in the Experience settings usually stabilizes text immediately.
Yes. Third-party screen-capture, overlay, or virtual-display drivers installed on the server hook frames before RDP encodes them and can make the whole desktop blink. Disable suspect drivers in Device Manager and reconnect to test.
It can, especially for video flicker on slow connections. 16-bit color halves the data per frame the encoder must push, which relieves the encode-decode chain. The trade-off is subtle banding in smooth gradients.
That points to the app's own rendering path, not the session. Apps with hardware acceleration enabled — browsers, chat apps, editors — can flicker remotely while the rest of the desktop is fine. Turn hardware acceleration off inside that app.
