Usually not. On most monitors, ARC and eARC are negotiated over a single shared return-audio connection between the display and the sound system.
Are you trying to keep one game console sounding full and cinematic while a streaming box or work laptop shares the same monitor without turning your desk into a cable-swapping mess? In most real setups, one practical rule decides the outcome: the monitor’s return-audio port, the sound system, and the monitor’s input map matter more than the name of the source device.
ARC and eARC on a monitor are not source-by-source features
The key point is that audio return over HDMI lets a display send sound back over the same cable, while eARC is the higher-bandwidth version of that same return path. That matters because ARC and eARC are not usually assigned separately to each console, streamer, or PC connected to the monitor. They are tied to the monitor’s single HDMI port labeled ARC or eARC, which then links to one soundbar or AVR.
In plain terms, if your monitor has one eARC-capable port, that port is the audio highway back to the sound system. Your console may feed video into HDMI 1 and your streamer may feed video into HDMI 2, but the return audio still exits through the same display-to-audio connection. You are not running one source on eARC and another on ARC as two independent live return channels on the same monitor.
This is why how eARC falls back to ARC can confuse buyers. Backward compatibility means an eARC port can fall back to ARC behavior when the audio device or settings support only ARC. It does not mean one source can reserve eARC while another uses a different return-audio mode on the same display at the same time.
What actually happens when multiple devices share one monitor
In most monitor-centered setups, the display works like a traffic manager. Your console, PC, or streaming stick sends video into the monitor, and the monitor sends audio back out to the soundbar or receiver through ARC or eARC. As audio return over HDMI explains, both devices must support the same feature level, and the HDMI port is usually labeled clearly.
The practical implication is simple. If your monitor and soundbar both support eARC, whichever source is active can potentially benefit from eARC-level return bandwidth, assuming the monitor can pass that format through. If the soundbar supports only ARC, or the monitor falls back to ARC for compatibility, every source using that return path is effectively limited by ARC behavior.
That weakest-link behavior is consistent across several references. how mixed support affects the return path and what happens when one device is limited to ARC point to the same result: if one side of the return chain is not truly eARC-capable, you drop to ARC limits. For gaming, that usually means compressed surround instead of the highest-quality lossless formats.
A simple example helps. Say a current game console is on the monitor’s HDMI 2.1 input for 4K at 120 Hz, and a work laptop is on an HDMI 2.0 input. The soundbar is plugged into the monitor’s eARC port. The monitor may switch active sources without issue, but the return-audio mode is still one monitor-to-soundbar relationship. It is not separately eARC for the console and ARC for the laptop as parallel states.
Where the confusion usually starts
Part of the confusion comes from mixing up HDMI input capability with return-audio capability. A monitor can have one fast input reserved for high-refresh console gaming and another standard input for secondary devices, and per-port HDMI limits for console gaming matter a lot for 4K at 120 Hz, VRR, and console mode behavior. But that is a video-input decision, not a sign that ARC and eARC are assigned independently per source.
Another source of confusion is product marketing. Retail pages for monitors with eARC support often frame the feature as a broad connectivity upgrade, which is directionally true, but they rarely spell out that most displays still expose only one return-audio path. In daily use, that means convenience improves, but routing flexibility is still narrower than on a full AVR.
Monitor design also matters. Testing-based monitor roundups show that most buyers still prioritize refresh rate, resolution, USB-C, and panel quality. ARC and eARC remain niche monitor features compared with TVs, so implementation details vary more than many buyers expect.
When it can still work well
Even though you usually cannot split ARC mode by source, you can absolutely build a setup that feels seamless. If the monitor and soundbar both support eARC, the best-case setup is straightforward: give the highest-performance HDMI input to the console that needs 4K at 120 Hz or VRR, connect the soundbar to the monitor’s eARC port, and let the monitor switch sources.
That arrangement works best when gaming is the priority and the second device is less demanding. KTC’s port-allocation advice lines up with that approach: reserve the best port for the device that benefits most from it, and move 4K at 60 Hz or office-focused gear to the lower-spec input.
If you mostly stream compressed Dolby Atmos or standard 5.1 audio, ARC may already be enough. audio return over HDMI notes that much Atmos content can travel over ARC when it is compressed, while eARC becomes more important for lossless formats such as Dolby TrueHD-based Atmos. For many monitor users, especially those alternating between gaming and productivity, that is the line that decides whether an upgrade is worth it.
When you should avoid relying on the monitor
A monitor becomes the wrong hub when you need guaranteed full-bandwidth audio from multiple premium sources or when the display does not clearly document passthrough behavior. That is where many users lose time in menus. Support-based troubleshooting across major device makers points to the same lesson: verify that every device in the chain really supports the passthrough standard you need before blaming the console or soundbar.
If your monitor lacks ARC or eARC, or if passthrough is inconsistent, the more reliable fix is often an HDMI audio extractor or a switch or splitter that handles the audio path directly. That workaround is less elegant, but it avoids asking a monitor to behave like an AVR. For streaming-box users, how to set up ARC or eARC with a TV and speaker system reinforces the same principle from another angle: the display must explicitly support ARC or eARC, and the feature must be enabled correctly before the rest of the chain can work.
A good rule of thumb is simple. If your setup includes a current console, a premium soundbar, and a second device that you also want on the same screen, a monitor with eARC can be clean and effective. If you need multiple sources with guaranteed top-tier audio behavior and fewer compatibility surprises, route sources through an AVR or an audio-capable HDMI switch instead.
The answer that matters at the desk
For most monitors, you should think of ARC or eARC as one shared return-audio lane, not one lane per device. Your console can still deliver excellent audio while another device shares the monitor, but both sources ride the same display-to-sound-system link, so the setup operates at whatever level that link actually supports.
If you want the setup to feel fast, immersive, and dependable, prioritize the best HDMI input for the console, confirm the monitor’s eARC passthrough behavior before buying, and do not expect one monitor to behave like two separate ARC systems at once.
