Quick answer
Sublime Text’s multiple selections let you edit several chosen locations together. Start with a narrow selection, add or skip occurrences deliberately, and review the resulting changes before testing the website. Use the current documentation and your actual key bindings because shortcuts differ by operating system and customization.
A fast editor action can repeat a mistake across a file. The most useful workflow combines precise selection with a small, reviewable change. This guide focuses on that editing task rather than a long list of extensions to install.
Begin with a working copy and a bounded change
Identify the file and the behavior you intend to change. Use the project’s development copy and version control process so the previous content can be recovered. Do not edit a live site merely because the file is accessible from the editor.
For an illustrative example, suppose three related CSS selectors need the same new class name. Search for the old name first and inspect its uses. A matching word in a comment, JavaScript reference or unrelated selector may need a different decision.
Add the next occurrence deliberately
Sublime’s official multiple-selection documentation describes Quick Add Next, Quick Skip Next and Undo Selection. On the documented default Windows and Linux bindings, Quick Add Next is Ctrl+D; on macOS it is Command+D.
Select the intended word and add the next occurrence. Inspect the highlighted text before typing. Skip an occurrence that should stay unchanged. If you selected too much, use Undo Selection or collapse to a single selection with Esc, then start again.
Using Find All selects every occurrence covered by that command’s scope. Use it only after checking that every selected location needs the same edit. A smaller selection is easier to verify when names repeat in several contexts.
Split a repeated block into line selections
The documentation also explains how to split a selected block into one selection per line. This can help with a short set of similarly structured lines, such as updating three related attribute values.
Inspect the beginning and end of every selected line. Unequal indentation or different text lengths can place carets in unexpected positions. After editing, read each complete line rather than checking only the changed characters.
Check bindings before copying a shortcut
The key bindings documentation explains how commands are assigned to keys and how contexts affect them. User settings and packages can change what a familiar shortcut does.
If an instruction fails, confirm the operating system, selected text and active bindings before installing a package or changing settings. The official documentation index provides separate references for projects, indentation and other editor features.
Review the diff and test the intended behavior
- Compare the file with its previous version.
- Confirm that only intended locations changed.
- Check syntax and any references to renamed selectors or values.
- Run the project’s relevant checks.
- Inspect the affected page and interaction in the development site.
For website work that needs a developer, a useful development request includes the page, current behavior, intended behavior and a reproducible example. The choice of editor can remain with the developer.
Key takeaways
- Inspect occurrences before editing them together.
- Use skip, undo-selection and Esc to keep the selection deliberate.
- Check operating-system and customized bindings.
- Review the complete diff and test the affected website behavior.
Frequently asked questions
Will the same shortcuts work on Windows and macOS?
Some default shortcuts differ. Check the documented platform binding and the editor’s current custom settings before following a shortcut-based instruction.
Should I replace every occurrence of a class name?
Inspect the references first. Different files or contexts may require coordinated changes, while an unrelated occurrence should remain unchanged.
Does this workflow require additional plugins?
The multiple-selection commands described here are documented editor features. Add packages only when a specific project requirement justifies them and their compatibility has been checked.

