Pen Settings



CSS Base

Vendor Prefixing

Add External Stylesheets/Pens

Any URLs added here will be added as <link>s in order, and before the CSS in the editor. You can use the CSS from another Pen by using its URL and the proper URL extension.

+ add another resource


Babel includes JSX processing.

Add External Scripts/Pens

Any URL's added here will be added as <script>s in order, and run before the JavaScript in the editor. You can use the URL of any other Pen and it will include the JavaScript from that Pen.

+ add another resource


Add Packages

Search for and use JavaScript packages from npm here. By selecting a package, an import statement will be added to the top of the JavaScript editor for this package.


Auto Save

If active, Pens will autosave every 30 seconds after being saved once.

Auto-Updating Preview

If enabled, the preview panel updates automatically as you code. If disabled, use the "Run" button to update.

Format on Save

If enabled, your code will be formatted when you actively save your Pen. Note: your code becomes un-folded during formatting.

Editor Settings

Code Indentation

Want to change your Syntax Highlighting theme, Fonts and more?

Visit your global Editor Settings.


                <p>This is a demonstration of how the &lt;label> element is used.  Notice that for examples where the &lt;label> is used correctly, a user can click on the prompt text to put the focus on the input control (or, in the case of radio buttons and check boxes, clicking will check/select the input item).</p>

<!-- INCORRECT: no label at all: when a user tabs to this field, all they'll hear is "edit" and no other indication of what they're supposed to type into the field -->
  <div>Enter Name: 
    <input type="text" name="txtName" size="15">

<!-- INCORRECT: missing for="", input needs a matching id=""; this has the same effect as above: screen-reader-user has no clue what to put into the field -->
    <label>Enter Phone#:</label>
    <input type="text" name="txtPhone" size="10">

<!-- CORRECT, BUT NOT 100% ACCESSIBLE: using for="" with matching input id=""
 TIP: you could also use aria-labelledby to make this more accessible, see WCAG ARIA16 -->
    <input type="checkbox" name="chkGotIt" id="chkGotIt">
    <label for="chkGotIt">I understand why we use label elements.</label>

<!-- CORRECT, BUT NOT 100% ACCESSIBLE: nesting the input element inside the label element, could also use ARIA16 here but it wouldn't make sense, just use the for/id instead -->
      <input type="checkbox" name="chkGoodForms">
      My HTML Forms will be accessible to all users.

<!-- CORRECT AND ACCESSIBLE: nesting and using for="" and id="" - support for everyone -->
    <label for="chkBest">
      <input type="checkbox" name="chkBest" id="chkBest">
      This is the best version.


                div {
  margin: .25em .1em;