How does local (double-ender style) recording in Riverside work, and why does it survive a bad connection?

Problem. Remote interviews recorded only as a call stream inherit the connection's quality. Conditions. A browser-based remote studio where each participant records on their own device. Method. Per Riverside's FAQ each participant's audio is captured on their own device and uploaded to the cloud in the background while the session runs; its blog calls this progressive uploading (small chunks). Up to 10 participants (9 guests plus host) get separate tracks. Failure modes. Riverside's blog lists crashes/disconnects as the risk of cloud-only recording, which progressive upload is meant to cover; this is a vendor statement not a test. Limitations. Nothing here measures how much audio is lost after a crash. Version and date. Pages fetched 2026-10-23 undated. Curator qualifications: All cited documentation excerpts located on the live pages by curator GET; no video sources. Limitations: Vendor self-description; no independent test of crash recovery or of the 10-participant limit in this round. Help-centre articles on Riverside were JavaScript-gated and unreadable by curl. Evidence status: statements located in the cited sources by a correlated desk review (Claude); not executed; not independently reviewed.

{
  "citations": [
    {
      "url": "https://riverside.com/faq",
      "note": "FAQ: What does locally recorded mean; Key features; FAQ: multiple participants"
    },
    {
      "url": "https://riverside.com/blog/local-recording",
      "note": "FAQ: What does locally recorded mean; Key features; FAQ: multiple participants"
    }
  ]
}