UXPin Keyboard Shortcuts

Mac Command (⌘) as the modifier. Canvas navigation, component and layer management, and prototype link creation.

Windows Ctrl as the modifier. Same shortcut structure as Mac.

Canvas navigation. Zoom in and out, fit the canvas to the window, and pan without activating a drawing tool.

Layer and element management. Selecting elements, grouping layers, duplicating, and stacking order management.

Component operations. Working with UXPin's component system — applying, detaching, and editing components.

Prototype interactions. Setting up click, hover, and other interaction triggers. Navigating between prototype screens.

Design system navigation. Switching between the canvas, the design system panel, and the component library.

A printable PDF of UXPin shortcuts is available for each platform.

Figma, Sketch, Zeplin, Overflow, and Principle sit near UXPin because design system work often connects interface design, component workflows, handoff, user flow documentation, and interaction prototypes. Figma and Sketch are common UI design environments, Zeplin supports design handoff, Overflow documents user journeys, and Principle focuses on motion and interaction design. These apps are related by workflow and audience, not because every UXPin workflow uses all of them.

How is UXPin different from Figma for shortcuts?

The shortcut structure is similar — both use canvas-based design with single-key tools and Command/Ctrl modifier combinations. UXPin's design system features (code component integration, design token management) have their own shortcut contexts not present in Figma.

This section lists official sources and documentation for UXPin. Use these references to verify shortcut behavior instead of relying on memory, old screenshots, or another person’s setup. They are especially helpful when comparing macOS and Windows, where the same design or prototype action may depend on different keyboard habits.

Official references are useful for checking platform differences, keyboard layout issues, browser conflicts, operating system shortcut conflicts, and app-version differences. A shortcut can be correct in one setup and still feel wrong because the OS, layout, or active context gets in the way. When something behaves differently than expected, verify it against the official source before updating personal notes, changing a team cheat sheet, or teaching the workflow.