Before downloading anything to repair an old setup, check which product you have. As of October 24, 2026, the Brackets repository says it is in maintenance mode, accepting security patches, with active development moved to Phoenix Code. Older Brackets instructions describe that editor's behavior; they do not establish that every current Chrome version works with every legacy build.
Open the folder before the page
Use File > Open Folder to open a small test project. Keep both files together:
pickup-note/
index.html
styles.css
Put this original fixture in index.html:
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width,initial-scale=1">
<title>Equipment pickup</title>
<link rel="stylesheet" href="styles.css">
</head>
<body>
<h1>Equipment pickup</h1>
<p>Collect the projector from Room 14.</p>
</body>
</html>
Put this in styles.css:
body {
max-width: 38rem;
margin: 2rem auto;
padding: 0 1rem;
font: 1rem/1.6 system-ui, sans-serif;
}
h1 { color: #254d69; }
Select index.html and start Live Preview. The meaningful first result is a heading and the Room 14 instruction with readable margins. These are expected results for the fixture, not a report of a Brackets session run here.
Change one visible value at a time
Change the room number to 16. Check the preview's instruction, then change the heading color in the linked stylesheet. That separates an HTML update problem from a stylesheet-path problem.
The Brackets usage guide documents live HTML/CSS updates in static preview, while other file types reload on save. It also says incomplete HTML syntax can pause updates. Finish a partially typed tag and inspect the preview indicator before assuming the browser connection is broken.
If the words update but the color does not, confirm that the loaded file links to styles.css and that you edited the stylesheet inside this project. If neither updates, save both files and reopen the selected HTML preview once. Keep the exact error message if that fails.
Use the real server for server-rendered pages
For an existing application, start its development server using the project's normal command. In File > Project Settings, set the Base URL to the address corresponding to the folder open in Brackets. The usage guide documents this custom-server route separately: server-processed pages update on save rather than receiving the same live HTML edits as the static preview.
A successful static fixture cannot establish that a PHP route, authenticated page, or API works. Compare the application's URL and response in an ordinary browser tab before changing Brackets settings.
Preserve the work if the legacy preview cannot connect
Save the source files and open the fixture in an ordinary browser to check its basic rendering. The browser HTML preview guide explains that fallback and the separate local-server route. A save-and-reload test still lets you inspect the document while investigating an editor-specific connection failure.
For a maintained editing environment, follow the current project links from the Brackets repository and assess the replacement against your existing files and extensions. Keep a copy of the project before changing tools. The immediate deliverable remains the saved HTML and CSS with the correct pickup instruction.