A wave of nostalgia (and a twinge of disappointment) has swept through the Mac community with the news that the very first developer beta of macOS 26 “Tahoe” appears to have removed support for FireWire 400 and 800 devices. This revelation comes from posts on social platforms—most notably a tweet by @NekoMichiUBC and various Reddit threads—and has been corroborated by hands-on testers who dug into the initial beta build. While this may be unsurprising given FireWire’s age, for those still holding onto legacy iPods, external drives, or older video equipment, it marks a potentially poignant end of an era.

Developers who installed the first macOS Tahoe beta reported that FireWire devices no longer mount or sync, and the familiar FireWire section in System Settings is conspicuously absent. In earlier macOS releases (including Sequoia and prior), users could manage FireWire settings or at least see the interface options; in Tahoe beta 1, that entire pane is gone. According to reports, attempts to connect first-generation iPods, MiniDV camcorders, or classic LaCie external drives via FireWire ports (or adapters) result in no recognition by the system.

It’s still early in the beta cycle. Apple frequently removes or alters legacy support in initial beta seeds, only to reinstate functionality later based on developer feedback or internal decisions. In communication with reporters, Apple was asked to confirm whether FireWire support has indeed been deprecated permanently; at the time of writing, there was no official response. Historically, Apple has quietly restored features or included workarounds in subsequent betas when there was sufficient use case or pushback. That said, with FireWire’s dwindling relevance and the fact that the last Mac model with a built-in FireWire port debuted in 2012, it would be understandable if Apple decided to fully phase it out now that Thunderbolt and USB variants dominate.

FireWire (Apple’s trade name for IEEE 1394) was conceived in the late 1980s as a high-speed serial bus to succeed parallel SCSI for digital audio and video workflows. The standard was ratified by the IEEE as IEEE 1394, with Apple, Sony, Panasonic, and Philips among the major contributors. In the early 2000s, it was celebrated for its sustained data rates—often outperforming USB 2.0 in practice—and its ability to power devices, making it popular for external hard drives, DV camcorders, and early iPods. In 2003, iPods began transitioning from FireWire to USB, but until about 2012, many Mac models included FireWire ports or could use adapters via Thunderbolt. Apple even sold Thunderbolt-to-FireWire adapters to maintain compatibility with pro audio/video gear and legacy storage.

Though FireWire is long past its prime, certain users remain attached to their legacy equipment: first-generation iPods (which many collectors cherish), older audio interfaces that rely on FireWire’s steady throughput, or archival drives storing data from years past. For professionals handling MiniDV footage or other specialized gear, the loss of native FireWire support complicates workflows, forcing reliance on older Macs, third-party PCIe expansion cards (where possible), or multi-adapter chains. Even hobbyists retrieving photos from vintage cameras or recovering old backups feel the sting when a simple cable no longer “just works.”

With native macOS support removed (or hidden) in beta 1, users will need to explore alternative approaches if they must access FireWire devices:

• Legacy hardware: Keep an older Mac running Sequoia (macOS 25) or earlier for FireWire tasks. Virtual machines cannot help here because the host hardware still needs physical FireWire connectivity.
• Adapters/expansion cards: For Intel Mac Pro users with available PCIe slots (increasingly rare), there may be third-party FireWire PCIe cards, though compatibility under newer macOS versions is uncertain. Thunderbolt-to-FireWire adapters may still function at a firmware level, but without OS support, they are moot.
• Networked solutions: Offload data via a network share from an older Mac to a newer one. For instance, mount FireWire drives on a legacy Mac, then transfer files over Ethernet or Wi-Fi to a machine running Tahoe.
• Alternative interfaces: Some audio and video vendors have released USB or Thunderbolt replacements for older FireWire devices. Investing in newer gear may be the long-term solution, albeit at cost.
• Community tools: Occasionally, enthusiasts develop kernel extensions or third-party drivers to resurrect deprecated ports; however, these often lag behind macOS updates and can pose security or stability risks.

While these workarounds exist, none are as seamless as built-in OS support. For casual users with sentimental hardware, the inconvenience may be tolerable. For professionals relying on FireWire daily, the change could necessitate workflow upheavals or hardware upgrades.

Apple’s hardware evolution has steadily favored universal, high-speed, and versatile connectors: Thunderbolt (now at version 4/USB4) and USB-C dominate modern Macs. Proprietary or legacy ports—FireWire, optical audio, even Ethernet on many models—have been jettisoned over the years. In macOS, Apple similarly phases out older APIs and hardware interfaces, nudging developers and users toward current standards. Deprecating FireWire fits this pattern: a technology introduced in the 1990s, last widely used in the early 2010s, and now effectively niche. Removing its support simplifies the OS codebase, reduces maintenance overhead, and aligns with hardware that no longer ships with FireWire ports.