Targeting & Conditional Logic

By the end of this page, you'll be able to scope any cursor or background to exactly the pages, devices, or elements you want.

Applies to Ultimate Cursor 2.3.1+.

Scope options

Value	Tier	Meaning
entire-website	free	applies everywhere
specific-pages	PRO	list of pages/paths
css-selectors	PRO	applies only inside matched elements
html-elements	PRO	applies only inside matched elements (element-picker variant)

Set this under Customize Your Cursor → Advanced (cursors) or the equivalent panel for backgrounds.

Page-match syntax

When using specific-pages, list entries can be:

• home or / — the site's front page
• a numeric post/page ID
• an exact slug or path (e.g. about, shop/hats)
• a prefix wildcard: foo/* matches anything under /foo/

There is no bare substring matching — foo alone won't match /foo/bar; use foo/* for that.

Device rules

Field	Type	Default	Behavior
hideCursorOnTouch	bool	on	hides the custom cursor on coarse-pointer (touch) devices
hideCursorOnMobile	bool	off	hides below ~600px width
hideCursorOnTablet	bool	off	hides between ~600–781px width

Touch detection uses pointer: coarse, not touch-capability APIs — this deliberately avoids hiding the cursor for mouse users on touchscreen laptops.

When configurations overlap

With multiple configurations (Pro), only one cursor is ever "main" at a time. Priority order: page-specific beats website-wide beats element-specific. If two page-specific configs both match the current page, only one renders as the main cursor — element-specific and CSS-selector-scoped cursors layer independently on top of whichever main cursor is active.