Game

Star Wars Jedi: Survivor on a Mac with a controller

Download InputConfig on the Mac App StoreThe Star Wars Jedi: Survivor layout is built into InputConfig, free on the Mac App Store. You don't have to make an account, there are no subscriptions, and nothing is locked. Optimized for Apple silicon.

On a Mac: No Mac version. Xbox Cloud Gaming carries it and reads your controller itself, and a Windows PC you stream from normally passes the pad through too.

Yes, Star Wars Jedi: Survivor plays on a Mac with a controller, through Xbox Cloud Gaming or a stream from your own PC. When the stream cannot see your pad, this layout rebuilds the console scheme from the keyboard binds: block on a trigger, tap it for a parry, push and pull on the bumpers. The timing-based combat plays fine, because a trigger tap is a trigger tap.

On this page: 9 sections
  1. The layout, control by control
  2. How the layout thinks
  3. Tune it
  4. If the stream passes your controller
  5. Star Wars Jedi: Survivor controller support: controller or keyboard
  6. If your controller is not working in Star Wars Jedi: Survivor
  7. Get it in two clicks
  8. Star Wars Jedi: Survivor controls: every button and the key it sends
  9. Questions

The layout, control by control

Click a control. Labels:

How the layout thinks

  • Move and look. The left stick moves, the right stick looks, and the left stick click is sprint.
  • Fight. The lightsaber attack (left click) is the left face button, and block and parry (right click) the right trigger. The special attack (F) is the top face button, and target lock the right stick click.
  • Move. Jump is the bottom face button and dodge (Tab) the right.
  • The Force. Push (2) is the right bumper and pull (3) the left. The Home button is Force slow (Ctrl).
  • D-pad. Up activates BD-1 (R), down heals (Q), left cycles the lightsaber stance (the scroll wheel), and right opens the binoculars (B).
  • Menus. The map (M) is on Create and Escape on Options.

Block is a held trigger and a parry is a tap of it, as on a pad.

Tune it

  • Stances back. D-pad left cycles stances one way. Add a chord that scrolls the other way.
  • Force slow elsewhere. If the Home button feels risky, press Scan on that row and move it to a back paddle.
  • Camera. Lower the look rows' Speed from 18 to about 14 and 10.

Move Force slow off the Home button if you ever hold it too long.

If the stream passes your controller

Xbox Cloud Gaming reads your pad itself, so there you play on the game's scheme and keep this preset off, or every press lands twice. Pick Xbox Cloud Gaming when you can, and keep this layout for a PC stream that cannot see the pad.

Star Wars Jedi: Survivor controller support: controller or keyboard

Steam's store page lists full controller support for Star Wars Jedi: Survivor, so the game was made to be played on a controller, menus included. A keyboard and mouse work as well, and the choice is yours. On a Mac, use the game's own controller support first when it sees your pad; this layout is for a pad it does not see, or for buttons it will not let you move. Full support listed means the controller is a first-class way to play Star Wars Jedi: Survivor.

From Steam's listing, checked in October 2026. Every game's listing is in Mac games with controller support.

If your controller is not working in Star Wars Jedi: Survivor

When Star Wars Jedi: Survivor does not react to your controller on a Mac, climb this ladder, smallest step first:

  1. Check that the Mac sees the controller. Open the gamepad tester and press a button. If nothing lights up there, the problem is the connection, and a controller that is connected but not working covers that first.
  2. Press a button after the stream has started. A stream only picks up a controller that is paired with the Mac, and a browser shows a controller to a page only after a button press. Start Star Wars Jedi: Survivor, then press any button.
  3. Play it from keys. If Star Wars Jedi: Survivor still ignores the pad, activate this layout. It sends the keyboard and mouse controls Star Wars Jedi: Survivor already reads. Turn the game's own controller option off while it runs, or a press can arrive twice. The layout works whether or not Star Wars Jedi: Survivor ever sees the controller.

Get it in two clicks

  1. Get InputConfig free on the Mac App Store, open it, and click Smart Preset Maker on the welcome screen.
  2. Search for Star Wars Jedi: Survivor and pick it. The layout is created as a preset in your sidebar, named and ready.
  3. Press Activate. Every row can be changed afterwards: the editor's Scan button rebinds any control the moment you touch it.

To check the controller itself first, the gamepad tester shows every button and stick live in your browser.

Star Wars Jedi: Survivor controls: every button and the key it sends

The Sends column is Star Wars Jedi: Survivor's default keyboard and mouse controls, as this layout expects them. If you changed a key in the game's settings, change the same row in InputConfig.

The Star Wars Jedi: Survivor preset in InputConfig, drawn on a DualSense Edge with each control labeled with the key or action it sends.
Figure 1. The Star Wars Jedi: Survivor preset drawn on a DualSense Edge in InputConfig's Live Visualizer. For example, X / Square is labeled Lightsaber attack (Left click), and Right trigger is labeled Block / parry (Right click). Any other controller shows the same layout on its own drawing.
ControllerSendsWhat it does
Left stick upWMove forward (W)
Left stick downSMove backward (S)
Left stick leftAMove left (A)
Left stick rightDMove right (D)
Right stick rightMouse motion right (speed 18)Look right
Right stick leftMouse motion left (speed 18)Look left
Right stick downMouse motion down (speed 18)Look down
Right stick upMouse motion up (speed 18)Look up
X / SquareLeft clickLightsaber attack (Left click)
Right triggerRight clickBlock / parry (Right click)
A / CrossSpaceJump (Space)
B / CircleTabDodge / evade (Tab)
Start / OptionsEscapePause / menu (Esc)
Y / TriangleFSpecial / power attack (F)
RB / R12Force push (2)
LB / L13Force pull (3)
L3 (left stick click)Shift (Left)Sprint (Shift)
R3 (right stick click)Middle clickTarget lock (Middle click)
Home / PS / GuideCtrl (Left)Force focus / slow (Ctrl)
D-pad upRActivate BD-1 (R)
D-pad downQHeal / stim (Q)
D-pad leftScroll upCycle lightsaber stance (wheel up)
D-pad rightBBinoculars / scan (B)
Back / Share / SelectMMap / shortcuts (M)

Button names follow the Xbox / PlayStation pair shown in the editor, so A / Cross is the bottom face button on either pad. On a Switch Pro Controller the bottom button is labeled B; the mapping still fires on position.

Questions

Does Jedi: Survivor run on a Mac?

Jedi: Survivor does not run natively on a Mac. Xbox Cloud Gaming streams it and reads the controller itself, and a Windows PC you own can stream it too. This layout covers a stream that does not see the pad.

Does Star Wars Jedi: Survivor have controller support?

Yes. Steam lists full controller support for Star Wars Jedi: Survivor, so every part of the game can be played on a controller.

Is Star Wars Jedi: Survivor better with a controller or a keyboard?

Both work. Steam lists full controller support for Star Wars Jedi: Survivor, so it was made to be played on a controller, and a keyboard and mouse work as well.

Why is my controller not working in Star Wars Jedi: Survivor on a Mac?

First check the Mac itself sees the controller, with the gamepad tester. If it does and Star Wars Jedi: Survivor still ignores it, activate the Star Wars Jedi: Survivor layout in InputConfig, which sends the game's keyboard and mouse controls from the controller.

Can I play Star Wars Jedi: Survivor on an M1 Mac or a MacBook Air?

Yes, through a stream. Star Wars Jedi: Survivor runs on the other end, on a cloud service or your own PC, so the Mac only plays the video and sends your input. An M1 MacBook Air streams it like any other Mac.

Download InputConfig on the Mac App StoreCompletely free. You don't have to make an account, there are no subscriptions, and nothing is locked. Optimized for Apple silicon. Open source on GitHub.

Updated