ARC Raiders is built around the idea that surviving the Rust Belt is better with a squad, and Embark knows most players don’t live on a single platform anymore. Whether you’re grinding loot runs on PC or dodging ARC fire on console, the game is designed to keep friend groups together instead of splitting them by hardware. Crossplay isn’t a side feature here, it’s part of the core co-op loop.
At a high level, crossplay in ARC Raiders means players on different platforms can party up, queue together, drop into the same matches, and extract as a unified squad. There’s no separate ecosystem or “crossplay-lite” mode. When it’s on, you’re sharing the same matchmaking pool and PvE encounters as everyone else.
Supported Platforms at Launch
ARC Raiders supports crossplay across PC, PlayStation 5, and Xbox Series X|S. PC players can squad up regardless of whether they’re launching through Steam or Epic Games Store, while console players are not locked to same-platform parties. A PS5 player can invite an Xbox Series X friend and a PC player into the same three-person squad without jumping through extra hoops.
Last-gen consoles are not part of the crossplay pool, which helps keep performance consistent and avoids hitbox or desync issues during high-intensity ARC encounters. Everyone you match with is running the same generation of hardware baseline, even if the input methods differ.
What Crossplay Actually Means in Practice
Crossplay in ARC Raiders isn’t just shared matchmaking, it’s full party integration. You can form a squad before matchmaking, load into the same instance, share revives, coordinate aggro, and extract together at the end of a run. Loot, progression, and mission completion all track normally, regardless of who’s on what platform.
Input-based matchmaking separation is not enforced in co-op PvE content. Mouse-and-keyboard and controller players can play together freely, which matters less in PvE but becomes important during contested extraction zones. The game balances difficulty around squad coordination and positioning, not raw aim advantage.
Crossplay Accounts and Friend Linking
ARC Raiders uses a unified Embark account system to power crossplay. Your platform account (PlayStation Network, Xbox Live, or PC storefront) is linked to an Embark ID, which acts as your universal identity across platforms. This is what allows cross-platform invites, friend lists, and party persistence to function smoothly.
You don’t need to re-buy the game on multiple platforms to play with friends, but your progression is tied to your Embark account, not the hardware. As long as your account is linked correctly, the game recognizes you no matter where you log in.
Crossplay Limitations to Be Aware Of
While crossplay is robust, platform-level features still exist. Voice chat quality and party overlays depend on in-game systems rather than console-native party chat when playing cross-platform. If someone relies on PlayStation or Xbox party chat, they’ll need to switch to ARC Raiders’ in-game voice to communicate with PC players.
Platform-specific friend invites also won’t work across ecosystems. Sending a PlayStation Network invite won’t reach a PC player, which is why using the in-game friend system is mandatory for crossplay squads. Most connection issues between friends come down to skipped account linking or outdated crossplay settings rather than server problems.
Account Requirements: Embark ID, Platform Accounts, and Cross-Progression Explained
With crossplay enabled and friend linking established, the next thing that actually makes or breaks cross-platform squads is how ARC Raiders handles accounts and progression. This is where Embark ID does the heavy lifting, acting as the glue between platforms, inventories, and long-term progression.
What an Embark ID Is and Why You Need One
An Embark ID is ARC Raiders’ universal account layer, and it’s mandatory for crossplay. Think of it as your true player identity, separate from PlayStation Network, Xbox Live, or your PC storefront. Friend lists, cross-platform invites, progression tracking, and matchmaking all key off this ID.
You’ll be prompted to create or sign into an Embark ID the first time you boot the game. If you skip or rush this step, crossplay technically stays enabled, but invites, friends, and progression syncing can behave unpredictably.
Linking Platform Accounts Correctly
Each platform account gets linked to your Embark ID, not merged with it. Your PSN, Xbox, or PC account is essentially a login method, while the Embark ID is where your data lives. This is why logging into the wrong Embark account on a second platform can make it look like your character vanished.
If you plan to play on multiple platforms, link them all to the same Embark ID before doing any serious progression. Unlocks, cosmetics, mission completion, and faction standing all pull from the Embark backend, not your local platform profile.
How Cross-Progression Actually Works
ARC Raiders supports full cross-progression across supported platforms, as long as you’re using the same Embark ID. Your loadouts, unlocked gear, crafting materials, and quest progress carry over automatically when you switch devices.
What doesn’t carry over are platform-locked entitlements, such as storefront-specific bundles or exclusive cosmetics. Those stay tied to the platform they were purchased on, even though your core progression remains shared.
Platform Compatibility and Party Creation Rules
All supported platforms can squad together with no PvE restrictions, but party creation always happens through the in-game friend list. Platform-native invites won’t bridge ecosystems, which is why adding friends via Embark ID is non-negotiable for crossplay.
Once friended, any player can invite others directly from the ARC Raiders social menu. Party leadership doesn’t affect matchmaking pools or difficulty scaling, so a console host and PC host behave identically from a backend perspective.
Common Account Issues and How to Fix Them
The most frequent crossplay problems come from mismatched Embark IDs. If a friend can’t see your invite or appears offline, double-check that both of you are logged into the correct Embark account and that crossplay is enabled in settings.
If progression appears missing, log out completely and relaunch the game to force a fresh account sync. In almost every case, missing gear or levels aren’t lost, they’re just tied to a different Embark ID than the one currently logged in.
How to Add Friends in ARC Raiders (Embark Friends vs Platform Friends)
Once you understand how Embark IDs power cross-progression, the next hurdle is learning how ARC Raiders actually handles friends. This is where a lot of squads get tripped up, especially if you’re coming from games that rely heavily on Steam, Xbox Live, or PlayStation Network for invites.
ARC Raiders technically supports platform friends, but only one friend system truly matters for crossplay: Embark Friends. Knowing the difference saves you from failed invites, invisible friends lists, and wasted prep time before a raid.
Embark Friends: The Only System That Works Across Platforms
Embark Friends is ARC Raiders’ universal social layer, and it’s the backbone of crossplay. When you add someone via their Embark ID, that connection exists at the backend level, not on any single platform.
To add an Embark Friend, open the Social menu in-game, navigate to Add Friend, and enter your friend’s Embark ID exactly as it appears. Once they accept, they’ll show up in your ARC Raiders friends list regardless of whether they’re on PC, Xbox, or PlayStation.
This is the only method that allows true cross-platform party invites. If your goal is to run extractions with mixed-platform squads, Embark Friends aren’t optional, they’re mandatory.
Platform Friends: Useful, but Limited
Platform friends still exist in ARC Raiders, but they’re sandboxed to their native ecosystem. Steam friends only show if both players are on PC, Xbox friends only appear when you’re both on Xbox, and the same applies to PlayStation.
These friends can be invited quickly if you’re on the same platform, but the moment one player switches devices, those connections stop working. Platform-native invites cannot pull players from another ecosystem into a party.
Think of platform friends as a convenience layer, not a crossplay solution. They’re fine for same-platform squads, but completely unreliable for mixed groups.
How Party Invites Actually Work
All party invites in ARC Raiders are sent from the in-game social menu, not your console dashboard or Steam overlay. Even if you’re both platform friends, the invite still routes through Embark’s backend once you’re in the ARC Raiders UI.
This is why players sometimes see friends online but can’t invite them. If someone isn’t added as an Embark Friend, the game can’t establish a cross-platform party, even if the platform itself says they’re online and available.
Once invited, party members persist between matches until disbanded. Switching hosts doesn’t affect matchmaking, enemy scaling, or loot tables, so pick whoever’s online first and deploy.
Common Friend List Issues and Fixes
If a friend doesn’t appear after being added, have both players restart the game to force a fresh social sync. ARC Raiders occasionally caches social data, especially after account linking or first-time logins on a new platform.
Make sure crossplay is enabled in the settings menu on both accounts. Disabling it hides cross-platform friends entirely, which can make it look like the friend request failed when it actually didn’t.
Finally, double-check Embark IDs for typos. Embark IDs are case-sensitive, and even a single incorrect character will prevent the request from going through, with no clear error message to warn you.
Creating a Crossplay Squad: Party Setup Step-by-Step
Now that you understand why platform friends aren’t enough, the actual party setup makes a lot more sense. ARC Raiders treats crossplay squads as an account-level feature, not a console feature, so every step happens inside the game’s own social layer.
Follow these steps in order, and you’ll avoid the most common desyncs and invite failures players run into.
Step 1: Confirm Crossplay Is Enabled on Every Account
Before sending a single invite, open the Settings menu and check the Crossplay toggle. This setting is account-specific and can be disabled without you realizing it, especially if you’ve been playing solo or testing PvP balance.
If crossplay is off, cross-platform friends won’t appear at all. The game doesn’t warn you, doesn’t gray them out, and doesn’t explain what’s wrong, so this step saves a ton of wasted time.
Step 2: Add Friends Using Embark IDs
From the main menu, open the Social tab and navigate to Add Friend. This is where Embark IDs matter, not gamertags, PSN names, or Steam usernames.
Embark IDs are case-sensitive and exact. If the request fails silently, it’s almost always a typo, not a server issue or privacy setting.
Step 3: Accept the Request In-Game
Friend requests must be accepted inside ARC Raiders. Platform notifications don’t count, and there’s no auto-accept even if you’re already friends on another system.
Once accepted, both players should see each other immediately in the Embark Friends list. If not, a quick restart forces a social refresh and usually fixes it.
Step 4: Send the Party Invite from the Social Menu
Select your friend’s name and choose Invite to Party. This invite is routed through Embark’s backend, meaning it works identically whether you’re on PC, Xbox, or PlayStation.
Do not use console dashboard invites or Steam overlays. Those only work for same-platform sessions and can break party visibility if used incorrectly.
Step 5: Verify Party Status Before Deploying
Once everyone joins, you should see all squad members listed in the lobby with ready status indicators. If someone appears but can’t ready up, have them leave and rejoin the party rather than re-inviting everyone.
Party leaders don’t affect matchmaking, enemy AI behavior, or loot RNG. The host is just a UI anchor, so whoever formed the party first is fine to stay in control.
Step 6: Launch and Stay Together Between Raids
After extraction or a failed run, the party persists by default. You don’t need to re-invite unless someone manually leaves or disconnects.
This persistence is crucial for crossplay squads grinding multiple deployments. As long as the party remains intact, you can tweak loadouts, swap roles, and redeploy without touching the social menu again.
Inviting Friends Across Platforms: In-Game Invites, Platform Invites, and Common Pitfalls
Once your party is formed and stable, this is where most crossplay squads either lock in smoothly or spiral into invite hell. ARC Raiders supports cross-platform play cleanly, but only if you use the systems the game actually recognizes.
Understanding which invite methods work, which ones don’t, and why things sometimes break will save you from re-adding friends or rebooting clients mid-session.
In-Game Invites: The Only Method That Always Works
The Social menu inside ARC Raiders is the backbone of crossplay. Any invite sent from here uses Embark’s servers, not your platform’s native systems.
This is why it doesn’t matter if you’re on PC and your teammate is on PlayStation or Xbox. As long as both players are friends via Embark ID, the in-game Invite to Party button is 100% platform-agnostic.
If an invite doesn’t show up, it’s usually because the receiving player is still loading menus or sitting in a post-raid state. Have them back out to the main lobby and the invite will typically appear instantly.
Platform Invites: When They Work and When They Break Things
Console dashboard invites, Steam friend invites, and system-level join options only function for same-platform players. They completely bypass Embark’s social layer.
If you’re playing cross-platform and send one of these invites, the game often fails silently. Worse, it can cause the invited player to appear “ghosted,” where they’re online but uninvitable until a restart.
As a rule, treat platform invites as off-limits unless everyone is on the same ecosystem. Mixing invite methods is the fastest way to desync your party state.
Joining Mid-Session and Why It Sometimes Fails
ARC Raiders does not support joining an active deployment. Extraction shooters rely on controlled spawns, enemy aggro states, and loot seeding, so mid-raid joins are locked out by design.
If someone crashes or disconnects during a run, they must wait until extraction or squad wipe to rejoin. No amount of re-inviting will override this.
The safest workaround is patience. Finish the raid, return to the lobby, then resend the party invite from the Social menu.
Crossplay Limitations You Should Actually Care About
There’s no platform-based matchmaking separation once crossplay is enabled. PC, Xbox, and PlayStation players share the same deployment pools.
This means mixed-input squads are normal. Mouse-and-keyboard players may have faster flicks, while controller users benefit from aim assist tuning, but the game’s TTK and hitbox design keep fights competitive.
Voice chat is also handled in-game. Do not rely on party chat from your console or Discord if you want everyone to hear callouts consistently during combat.
Common Pitfalls That Stop Parties from Forming
Privacy settings are a silent killer. If your Embark account is set to Friends Only or Private, cross-platform invites can fail without any error message.
Version mismatches are another issue, especially right after patches. If one player hasn’t updated, they’ll appear online but be impossible to invite.
Finally, avoid rapid invite spamming. ARC Raiders throttles social actions, and sending multiple invites too fast can temporarily lock the button, making it seem like the system is broken when it’s just cooling down.
Crossplay Limitations & Restrictions (Voice Chat, Input Methods, Matchmaking Rules)
Even when your party finally sticks, ARC Raiders still enforces a few hard rules that shape how crossplay actually feels in live deployments. These aren’t bugs or temporary quirks—they’re baked into how the game balances fairness, communication, and server load across platforms.
Voice Chat: One System, No Safety Nets
ARC Raiders uses a single, built-in voice chat system for all crossplay squads. Platform party chat, console system chat, and Discord overlays do not pipe audio into the game’s proximity or squad channels.
If one player can’t hear callouts, it’s usually because their in-game voice chat is muted, misconfigured, or overridden by a console-level audio setting. Crossplay squads live or die by in-game comms, especially when coordinating aggro pulls or last-second extractions, so double-check mic input and output before deploying.
Push-to-talk behavior also differs slightly between PC and console. PC players can fine-tune thresholds, while controller users are more dependent on open mic sensitivity, which can cause clipped callouts if not adjusted.
Input Methods: Mixed by Design, Not Separated
ARC Raiders does not split matchmaking by input method. Mouse-and-keyboard and controller players share the same lobbies, even in full crossplay deployments.
Controller users benefit from aim assist tuned for mid-range tracking, while mouse players retain faster flick potential and tighter recoil control. The balance comes from ARC Raiders’ relatively grounded TTK, readable hitboxes, and limited I-frame abuse, which prevents raw input advantage from completely dominating firefights.
There is no option to lock matchmaking to controller-only or mouse-only when crossplay is active. If your squad is mixed-input, you’re opting into that ecosystem by default.
Matchmaking Rules: Party Leader Dictates the Pool
In crossplay parties, the platform of the party leader determines nothing about matchmaking pools. Once crossplay is enabled, all squads are matched globally across PC, PlayStation, and Xbox.
What does matter is squad size and deployment timing. Solos, duos, and trios are matched separately to preserve encounter pacing, so adding or removing a single player changes the pool you’re queued into.
Skill-based matchmaking exists, but it’s loose by extraction-shooter standards. Expect wide skill variance, especially during off-peak hours, and understand that crossplay expands the pool rather than tightening it. That’s intentional, keeping raids populated and extraction windows active instead of forcing long queues.
If you’re trying to minimize friction, keep your party consistent, avoid swapping leaders mid-session, and always regroup in the lobby before re-queuing. ARC Raiders rewards squads that respect its systems instead of fighting them.
Troubleshooting Crossplay Issues: Friends Not Showing, Invite Failures, Region Mismatches
Even when crossplay is enabled and everyone’s settings look correct, ARC Raiders’ social systems can still throw friction into the mix. Most issues stem from how the game syncs platform accounts, regions, and party states in real time.
Before assuming something is broken, treat crossplay problems like any other live-service hiccup: isolate the variable, reset the connection point, and make sure everyone’s operating under the same ruleset.
Friends Not Showing Up on Your List
If a friend isn’t appearing in your ARC Raiders social menu, the first thing to verify is account linking. Crossplay relies on the game’s central account system, not just PlayStation Network, Xbox Live, or Steam friends lists. If one player hasn’t completed account linking, they’ll be invisible outside their native platform.
Next, confirm that both players have crossplay enabled in the settings menu. ARC Raiders treats crossplay as an opt-in system, and if even one person has it disabled, cross-platform friends won’t populate or be searchable.
If everything looks correct, have both players return to the main menu or restart the client. Friend lists refresh on login, not dynamically, so staying logged in while someone changes settings can cause desyncs.
Invite Failures and Party Join Errors
Invite failures usually happen when the party state isn’t clean. If someone is stuck in a post-raid results screen, reconnecting from standby, or mid-queue, invites can silently fail without throwing an error.
The safest fix is to fully disband the party, have everyone return to the main lobby, and then send fresh invites from the same player. ARC Raiders handles party authority strictly, and leftover session data can block new joins.
Also watch for platform-level overlays. Console players sending invites through system menus instead of the in-game social panel may run into conflicts. Crossplay invites should always be sent from inside ARC Raiders, not through PlayStation or Xbox UI shortcuts.
Region Mismatches and “Can’t Join Party” Messages
Region mismatches are one of the least obvious but most common crossplay problems. ARC Raiders automatically assigns a server region based on latency, and parties can fail to form if players are locked to incompatible regions.
If you’re playing with friends overseas, check the region setting in the network or matchmaking menu and manually align everyone to the same region when possible. Expect slightly higher ping, but party stability matters more than perfect latency in extraction shooters.
Region issues also pop up during off-peak hours. If matchmaking can’t find a viable server that fits the entire squad, the game may block party creation altogether. Switching regions or waiting a few minutes often resolves it.
Version Mismatch and Update Desyncs
Crossplay only works when everyone is on the exact same game version. PC patches can roll out slightly faster than console updates, creating a short window where cross-platform parties simply won’t connect.
If one player can’t accept invites at all, double-check for pending updates or partially installed patches. A full client restart after updating is critical, especially on consoles that resume games from sleep.
When in doubt, assume the problem is state-related, not skill-related. ARC Raiders’ crossplay systems are robust, but they expect clean inputs, synced accounts, and players who respect how the backend stitches platforms together in real time.
Best Practices for Smooth Co-Op Runs in ARC Raiders (Settings, Comms, and Squad Roles)
Once your squad is actually formed and inside the same lobby, the real work begins. ARC Raiders is brutally unforgiving to uncoordinated teams, especially in crossplay squads where hardware, controls, and audio setups vary wildly. Locking in the right settings, communication habits, and squad roles is the difference between clean extractions and wiping to bad info.
Dial In Crossplay-Friendly Settings Before Dropping
Start with audio and interface settings, because information wins fights in ARC Raiders. Enable directional audio and reduce non-essential sound effects so footsteps, ARC movement cues, and gunfire aren’t buried under ambient noise. Console players should double-check headset mixing at the system level, since platform audio balancing can override in-game sliders.
Turn on squad markers, ping confirmations, and damage indicators. These features are essential for crossplay teams, especially when PC players have faster target acquisition while controller users rely more on visual callouts. Shared visual language keeps everyone synced regardless of input method.
If you’re seeing desync or stutter mid-run, lower visual effects rather than resolution first. Particle-heavy ARC encounters can spike performance inconsistently across platforms, and smoother frames matter more than sharper textures when reacting to aggro shifts.
Use Clear, Platform-Agnostic Communication
In-game voice chat is the safest option for crossplay squads. Third-party apps can work, but they often introduce latency, echo, or platform-level conflicts that don’t show up until combat starts. ARC Raiders’ built-in comms are designed to sync with squad actions and proximity events.
Keep callouts short and standardized. Use terms like “ARC left flank,” “reload window,” or “extract pad hot” instead of long explanations. Crossplay squads don’t always process info at the same speed, so clarity beats detail every time.
When voice fails, pings are your backup. Get in the habit of pinging threats, loot, and movement paths even while talking. Visual pings cut through language barriers, mic issues, and background noise, which are all more common in mixed-platform parties.
Assign Squad Roles to Minimize Crossplay Friction
Every ARC Raiders squad should define roles before deployment. A scout handles forward vision and pings, a damage-focused player controls ARC DPS during engagement windows, and a support-minded player manages revives, positioning, and extraction timing. These roles don’t lock players into builds, but they give structure under pressure.
PC players often excel as scouts due to faster camera control and precision aiming, while console players may thrive in anchor roles that focus on area control and sustain. This isn’t about skill gaps, it’s about leveraging each platform’s strengths inside the same sandbox.
Rotate roles between runs to avoid burnout and adapt to RNG. ARC spawns, loot density, and enemy behaviors shift constantly, and rigid squads break faster than flexible ones. A team that adapts roles mid-session survives longer.
Respect Extraction Timing and Shared Risk
Extraction is where crossplay squads fail most often. One player lagging behind or pushing greedily can pull aggro onto the entire team, and platform input differences can exaggerate reaction delays. Call extraction early and commit together.
Never assume everyone sees the same thing at the same time. Minor latency differences can change how ARC movement or projectile timing looks across platforms. If one player calls danger, trust it and reposition first, ask questions later.
At the end of the day, ARC Raiders rewards squads that think like a unit, not three solo players sharing a lobby. If your team communicates cleanly, respects platform differences, and plays roles instead of egos, crossplay becomes a strength rather than a hurdle. Survive together, extract together, and the game opens up in ways solo runs never will.