Skip to the lesson
ChalkLineclear audio for people who teach online

ChalkLine

About ChalkLine

A small publication about one narrow, stubborn problem: sounding clear when you teach online. Written for tutors, teachers and webinar hosts by an editorial team that has taught the 7 a.m. conversation slot and has the calendar scars to prove it.

Who writes this

ChalkLine is written and maintained by a small editorial team. We publish under the team byline rather than inventing friendly faces with stock-photo smiles — you'll never see a fabricated staff page here. What we'll tell you instead is what shapes the judgment on these pages: time spent teaching on marketplace platforms, hosting webinars, and reviewing a frankly unhealthy number of our own lesson recordings.

What we cover — and the fence around it

The software side of teaching audio: noise suppression layers, platform classroom mechanics, browser and device-picker plumbing, recording quality, and the classroom habits that software can't replace. The fence is deliberate:

  • No hardware. No microphone round-ups, no headset deals. Other sites do that; we'd rather be the ones who know the software chain cold.
  • No generic meeting-app tutorials. Zoom, Teams and Meet document their own menus exhaustively. Where a teaching platform runs on one of them, we write the teaching layer those docs skip.
  • No pretend testing. We don't run a lab and won't invent one. Where we score tools, the scoring model is a script that ships with this site (tools/fit-score.py) — inputs, weights and reasoning included — so you can disagree with it precisely.

Why so narrow

A fair question: why would anyone run a whole publication on teaching audio software? Because breadth is where this topic goes to die. General tech sites cover noise cancellation as a features war; teaching sites cover audio as an afterthought paragraph between lesson-planning tips. The actual working teacher — deciding at 11 p.m. whether $8 a month will stop students asking "sorry, what?" — falls between those stools. A narrow site can do the unglamorous things that situation needs: re-check one vendor's pricing page monthly, keep a register of every fragile fact with its verification date, and write the Outschool mute-ritual section that no general site would bother with. Narrowness is the feature.

It also keeps us honest about pace. Platforms change quietly — a classroom gets a new device picker, a recording feature changes its browser support — and a narrow beat means we notice. When you find a page here whose verification date has aged past a platform update, that's the corrections address below earning its keep.

How we verify

  • Vendor facts come from vendor pages, checked on a stated date. Every price, plan limit and platform feature on this site carries its verification date (current pass: 2026-09-20). If a fact ages, the date tells you exactly how much.
  • When primary sources are ambiguous, we print the hedge. Example you'll meet on our pages: Krisp's long-running free daily plan no longer appears on its pricing page as of our check — so we say precisely that, rather than repeating what old reviews remember.
  • Limitations get stated. Every recommendation on this site comes with the list of things it won't fix. If a page seems to be missing that list, that's a bug — tell us.

How the site makes money

Some links — clearly marked, always disclosed where they appear — are affiliate links: if you start a paid plan through one, ChalkLine may earn a commission at no extra cost to you. Two structural honesty checks on that: our scoring is computed by the shipped script and doesn't know which row pays us, and our standing advice includes recommendations that pay us nothing — the platform defaults we tell most quiet-room teachers to stop at, and NVIDIA Broadcast, with which we have no relationship at all. The full policy lives in the Classroom Rules.

Corrections. Found a fact that's drifted, a price that's changed, or a platform behavior we've described wrongly? We'd genuinely rather know: [email protected]. Errors get fixed on the page with the verification date updated — quietly if trivial, with a note if load-bearing.