Retest PC

Headphone Burn-In

Plug in the headphones, set a normal listening level, press Start burn-in and take them off. The program cycles through noise, sweeps and rests for as long as you choose.

Headphones, earbuds and IEMsRuns in a browser tab
Run for
Output
Elapsed
0:00:00
Remaining
4:00:00
Ready. Press Start burn-in.
One 30 minute cycle, repeatedCycle 1 of 8
Pink
Sweeps
Rest
Brown
Bass
White
Rest
Whole program0%
40%

Listen for a few seconds at the start and set the level you normally listen at, or lower. Then take the headphones off.

Keep the screen awake
Total so far, all sessionsGoal 40 h
0.0hours
Playing now
Nothing yet
Next: pink noise
Cycle
0
Of 8 in this program
Level
-32.0dBFS
Noise RMS, before system volume
Program
4h
8 cycles of 30 minutes
Everything plays from this tab. Nothing is recorded or sent. Keep the tab open and the computer awake until it finishes.

This headphone burn in tool plays a timed burn-in program, made in your browser instead of a downloaded track: pink noise, brown noise, white noise, full range sweeps, bass sweeps and quiet rests, repeated in a 30 minute cycle for 1 to 48 hours. A progress display shows what is playing, the time left and how many hours your headphones have run in total, across sessions. It works with wired and wireless headphones, earbuds and in-ear monitors, on Windows, Mac and Linux. Below the tool is a plain account of what burn-in can and cannot change.

How to burn in headphones with this tool

  1. Connect the headphones and check that your computer plays through them.
  2. Choose how long to run: 1, 4, 8, 12, 24 or 48 hours.
  3. Press Start burn-in, put the headphones on for a few seconds and set the Volume to your normal listening level or a little below.
  4. Take the headphones off and leave them on a desk or stand. Do not wear them while the program runs.
  5. Leave the tab open. Keep the screen awake stops the computer sleeping and cutting the sound.
  6. Pause and resume whenever you like. The total under the button adds up across sessions in this browser.

What the program plays

Each 30 minute cycle runs these parts in order, with short fades between them so the driver never sees a sudden jump:

Part Length Why it is there
Pink noise 10 min Even energy in every octave, the standard broad signal
Sweeps, 20 Hz to 20 kHz and back 3 min Moves the driver through its whole range in turn
Rest 2 min Silence, so the driver and amplifier cool
Brown noise 6 min Heavier on bass, larger slow cone movement
Bass sweeps, 20 to 200 Hz and back 3 min Works the low range, where the suspension moves most
White noise, 6 dB quieter 4 min Treble energy, kept lower so the top end is not pushed hard
Rest 2 min Silence

Pink and brown noise play at the same average level, the sweeps 3 dB below them and white noise 6 dB below, so the volume you choose stays comfortable through the whole cycle.

What the readouts mean

Readout What it tells you
Elapsed and Remaining Time played and time left in this run. They stop while paused
Playing now The current part and how long it has left
Cycle Which 30 minute cycle is running, out of the total
Level The average level of the noise before your system volume, for example −32 dBFS
Total so far Hours played across all sessions in this browser, against a 40 hour mark

Does headphone burn-in work?

Here is what is known, without the marketing:

  • Drivers can loosen a little. In loudspeakers, the suspension around the cone gets more flexible with use, which lowers the bass resonance. Speaker makers often run new woofers before measuring them for this reason. Headphone drivers are much lighter films with far less suspension, so the effect is smaller.
  • Measured changes are small. Reviewers who have measured headphones before and after burn-in runs have mostly found changes of a fraction of a decibel, often within the variation you get from taking the headphones off and putting them back on.
  • Ear pads change more. New pads are firm and compress over the first weeks of wear, which changes the seal and the bass. That happens from wearing them, not from noise playing on a desk.
  • Your hearing adapts. After a few days with a new pair, your brain gets used to its tonal balance. Many people hear that as the headphones "opening up".

So burn-in will not harm headphones at a sensible level, and it may settle a new driver slightly, but it will not turn one pair into another. If a new pair sounds wrong, check the fit first.

The headphones sound different after a few days

That is usually your ears adjusting, or the pads softening. To check whether anything changed in the headphones, compare them with the same music at the same volume, or listen for the point where the bass fades on a frequency sweep before and after. A real change that you can mark on a sweep is rare.

One side sounds different or quieter

Run the program on Left or Right only if you want to work one driver, but first find out why they differ. Check the balance in your sound settings and the fit of each ear cup or tip, then run the left right audio test and the headphone test. A side that is quieter, buzzes or cuts out when you move the cable has a fault that burn-in cannot fix; see headphones not working.

Safe settings for burn-in

  • Use your normal listening level or lower. Louder does not burn in faster.
  • Do not wear the headphones during the program, and keep them away from pets, who hear higher pitches than we do.
  • Turn off noise cancelling and sound effects so the drivers get the plain signal.
  • Keep wireless headphones charged, and the computer plugged in and awake.
  • Start with a short run on a new pair and listen for any buzz before leaving it for hours.

What a browser burn-in cannot do

The tool plays exact, repeatable signals, but it cannot measure your headphones or tell you when they are "done". It also needs the tab to stay open: if the computer sleeps or the browser closes, the program stops and the total keeps the time already played. Phones often pause web pages when the screen locks, so a computer is the better choice for long runs. For pink noise on its own, with a sleep timer, use the pink noise page.

Headphone burn-in questions

How long should I burn in headphones?

If you want to do it, JLab, one maker that recommends burn-in, suggests about 40 hours. There is no need to run it in one go: split it over several sessions, and the tool keeps a running total in this browser.

Can burn-in damage headphones?

Not at a normal listening level. Damage comes from volume, not hours: very loud noise or deep sweeps can overheat a driver or make it hit its limits. Keep the level at or below what you listen to music at, and never turn it up because you cannot hear it with the headphones off.

Is pink noise or music better for burn-in?

There is no evidence either is better. Pink noise and sweeps exercise the driver evenly across the range in a predictable way, which is why burn-in tracks use them. Playing your normal music for the first weeks does the same job while you enjoy it.

Do wireless earbuds need burn-in?

No more than wired ones. Their tiny drivers have very little suspension to loosen, and their sound is mostly shaped by the fit of the ear tips and by built in processing. Getting the right tip size makes a far bigger difference.

Can I leave the burn-in running overnight?

Yes. Keep the page open, keep the computer awake, plug in the power, and set a moderate level. For wireless headphones, keep them charged and close to the computer so the connection does not drop.

Is headphone burn-in a myth?

Partly. Drivers can change slightly in their first hours of use and ear pads soften over weeks, both of which are real. But measured changes in modern headphones are small, and much of the difference people hear after a few days is their own ears getting used to a new sound.