Tl;dr
- Choose Foxglove if you want a modern, team‑ready platform that plays .bag / .db3 / .mcap, merges multiple files into one timeline, streams live ROS via foxglove_bridge, and now includes a C++/Python/Rust SDK to stream or log directly to MCAP.
- Keep RViz for interactive markers and local ROS debugging inside the ROS environment—RViz remains the canonical ROS GUI for in‑scene manipulation.
At‑a‑glance: RViz vs Foxglove.
| Category |
Foxglove |
RViz / RViz2 |
| Platform |
Web + Desktop |
Desktop (ROS env) |
| Live ROS |
foxglove_bridge (ROS 1) SDK (ROS 2) over WebSocket |
ROS-native GUI |
| File playback |
.bag / .db3 / .mcap; multi-file merged timeline |
Uses rosbag / ros2 bag for playback |
| 3D & Interactions |
Modern 3D scene; visualizes markers |
Interactive markers (move/rotate/context menu) |
| Collaboration |
Layouts, Devices, Events, Timeline |
Local, single-user focus |
| SDK / Extensibility |
Foxglove SDK (C++ / Py / Rust, MIT); Extensions |
C++ plugins, interactive markers |
Head‑to‑head
1) Live ROS connectivity.
- Foxglove: Connect ROS 1 via foxglove_bridge (WebSocket) ROS 2 via the SDK. Works from desktop or the browser—great for remote reviews.
- RViz: Tightest ROS integration, ideal for local debugging. Interactive markers enable direct 3D manipulation inside RViz.
2) File playback & formats.
- Foxglove: Drag‑and‑drop ROS 1 .bag, ROS 2 .db3, and MCAP. Open multiple files as a single merged timeline. For legacy .db3, Foxglove suggests converting to MCAP for self‑contained metadata.
- Context: ROS 2 Iron set MCAP as the default rosbag2 storage, simplifying cross‑tool workflows.
3) 3D & interaction model.
- RViz: Interactive markers (move/rotate/context menus) are native and powerful for in‑loop manipulation.
- Foxglove: Modern 3D visualization with synchronized panels; teams often handle interactions via publish/teleop and rich panels rather than RViz‑style marker primitives.
4) Collaboration and scale.
- Foxglove: Built for teams—Layouts, Devices, Events, and a fast Timeline for browsing large datasets. Free plan: 3 users / 10 devices / 10 GB cloud.
5) Extensibility and SDKs.
- Foxglove: Extensions (JS/TS) for custom panels/converters and new data loader extensions; Foxglove SDK (C++/Py/Rust, MIT) to stream or log to MCAP.
- RViz: C++ plugin system; broad community of displays and tools.
Migration quick‑start (RViz → Foxglove).
- Open data: drag .bag/.db3/.mcap—or load multiple files merged into one timeline.
- Connect live: run foxglove_bridge (ROS 1) SDK (ROS 2) and open the WebSocket in Foxglove.
- Add context: organize by Devices, annotate Events, and explore via Timeline.
- Programmatic ingest: use the Foxglove SDK (C++/Python/Rust) to stream live or log to MCAP.
FAQs
Q: Is Foxglove a full replacement for RViz?
A: For many team workflows (file analysis, remote reviews, shared layouts), yes. For interactive marker manipulation inside ROS, RViz still shines.
Q: Can Foxglove open ROS 2 .db3 and MCAP?
A: Yes—.db3 and .mcap are supported; Foxglove recommends MCAP for portability.
Q: How do I connect ROS 2 to Foxglove?
A: Use foxglove_bridge for a stable, high‑performance WebSocket path.
Try it out for yourself today: https://foxglove.dev/signup
