GITNUXSOFTWARE ADVICE
General KnowledgeTop 10 Best Internet Radio Broadcast Software of 2026
Top 10 internet radio broadcast software with side-by-side comparisons of Radio.co, RadioDJ, SAM Broadcaster, plus shortlist picks.
How we ranked these tools
Core product claims cross-referenced against official documentation, changelogs, and independent technical reviews.
Analyzed video reviews and hundreds of written evaluations to capture real-world user experiences with each tool.
AI persona simulations modeled how different user types would experience each tool across common use cases and workflows.
Final rankings reviewed and approved by our editorial team with authority to override AI-generated scores based on domain expertise.
Score: Features 40% · Ease 30% · Value 30%
Gitnux may earn a commission through links on this page — this does not influence rankings. Editorial policy
butt is the best pick for small stations that want a reliable desktop desktop source client with metadata and reconnection for live streaming, whereas Broadwave Streaming Audio Server suits teams running broadcasts from a Windows PC while handling encoder and automation elsewhere, and if you’re watching budget, RadioDJ is a solid free-entry option for scheduled playback with controlled on-air metadata.
Editor’s top 3 picks
Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.
butt
Integrated encoder-to-stream pushing with built-in metadata updates and reconnection logic aimed at keeping the live mount fed.
Built for fits when small stations need a reliable desktop source client with metadata and reconnection for live streaming endpoints..
Broadwave Streaming Audio Server
Editor pickServer-side stream endpoint management with mount-style publishing behavior for long-running live broadcasts.
Built for fits when station staff manage encoder and automation elsewhere, and need governed server endpoints for listeners..
Mixxx
Editor pickDeck-based live mixing with direct stream output keeps performance behavior consistent during on-air transitions.
Built for fits when small teams run live shows from one machine and need integrated mixing plus streaming..
Related reading
Comparison Table
butt
encoderLightweight audio streaming tool for broadcasting to SHOUTcast and Icecast servers.
Integrated encoder-to-stream pushing with built-in metadata updates and reconnection logic aimed at keeping the live mount fed.
butt works as a source client that pulls audio from local files or capture devices and then pushes it to a streaming server using a configured encoder chain. Metadata injection is handled per stream so the listener-facing titles can update alongside the audio workflow. Configuration is file-based and repeatable, which helps when the same stream setup must run across similar stations or remote studios.
A tradeoff appears when a station needs playlist scheduling, crossfading, or full broadcast automation with scheduled events, because butt centers on feeding an encoder output rather than running a timeline of programmed shows. butt fits well when a small ops team needs a stable “always-on” contributor source for an existing Icecast or Shoutcast deployment, including during mount point interruptions that require reconnection logic.
- +Solid source-client streaming workflow with dependable reconnect handling
- +Metadata injection updates listener-visible titles without extra tooling
- +Local audio capture and encoding are managed in one desktop process
- +Repeatable configuration files simplify station cloning and recovery
- –Limited built-in playlist scheduling compared with dedicated automation tools
- –Requires manual integration effort for multi-stream relays and complex routing
- –Does not provide multi-user RBAC or web admin governance
- –Advanced show workflows often need external playlist or traffic systems
Community radio ops
Always-on feed from local studio
Fewer dropouts during brief outages
Podcast-to-live producers
Convert file playlists into radio stream
Consistent stream output for listeners
Show 2 more scenarios
Small event broadcasting teams
Rapid setup for temporary stations
Faster start with repeatable configs
Loads a saved stream configuration and begins pushing audio to a pre-provisioned endpoint for events.
Third-party broadcast contributors
Remote source delivery to a station
Drop-in contribution with proper titles
Sends encoded audio from a remote location while maintaining metadata updates for the hosting station.
Best for: Fits when small stations need a reliable desktop source client with metadata and reconnection for live streaming endpoints.
More related reading
Broadwave Streaming Audio Server
SMBWindows-based streaming audio server for running internet radio broadcasts from a PC.
Server-side stream endpoint management with mount-style publishing behavior for long-running live broadcasts.
Broadwave Streaming Audio Server is best aligned with teams that already have an encoder workflow and want a stable streaming server layer for a radio signal. Configuration centers on the streaming server process and stream endpoint behavior so the server can remain reachable and consistent for listeners. It fits deployments that expect operations control over uptime, network settings, and stream source handling rather than a web-only broadcast console.
A key tradeoff is that Broadwave concentrates on the streaming server role and does not replace broadcast automation tools for playlist scheduling and on-air control. It works well when combined with an automation engine that produces the live source feed and handles track timing and metadata injection. For teams running a single station or a small cluster, this split reduces complexity while keeping the listener-facing endpoint governed in one place.
- +Clear streaming server configuration for consistent listener-facing endpoints
- +Good fit for manual operations when encoder and source workflow is already defined
- +Reliable server-side handling for continuous live listener access
- +Works as a dedicated layer behind an external automation workflow
- –Limited built-in automation for playlist scheduling and DJ control
- –Requires careful server and source configuration discipline for stable output
- –API surface for deep automation integration is not a primary strength
- –Admin experience depends on server-side configuration rather than guided console workflows
Broadcast engineering teams
Maintain a consistent live listener endpoint
Fewer listener dropouts
Small station operators
Run one live channel reliably
Stable on-air availability
Show 2 more scenarios
Automation integrators
Pair with external schedulers
Cleaner separation of duties
Receives the live feed from another system and publishes it as a governed stream endpoint.
Streaming operations
Support scripted source switching
Predictable transitions
Provides an operational target for controlled source behavior during live transitions.
Best for: Fits when station staff manage encoder and automation elsewhere, and need governed server endpoints for listeners.
Mixxx
open-sourceOpen-source DJ software with live broadcasting support for internet radio streams.
Deck-based live mixing with direct stream output keeps performance behavior consistent during on-air transitions.
Mixxx runs as a desktop application with audio-engine routing that lets a DJ mix feed directly into an Icecast-style streaming workflow. The software includes library management, deck controls, crossfading, and cueing tools that reduce the need for separate playback consoles for basic shows. Stream output is configurable at the encoder layer, with settings for format, bitrate, and buffering behavior to match a station’s encoder configuration requirements.
A tradeoff is that Mixxx is not a centralized web broadcast console for multi-admin governance, so operations like multi-user stream key management and audit trails are limited compared with broadcast suite products. Mixxx fits best when one host or small team runs shows from a single machine and needs consistent live mixing, source switching, and stream output without deploying a full server-and-console stack.
- +Live mixing and streaming output share the same low-latency audio engine
- +Device routing supports fast input switching for on-air segments
- +Crossfades, cues, and deck workflows reduce external playback tooling
- +Open extensibility via community scripts and audio processing plugins
- –Limited multi-admin RBAC and audit log features for station governance
- –Automation depth is weaker than dedicated broadcast automation servers
- –High-throughput multi-stream operations require additional architecture
- –Operational reliability depends on local machine uptime and audio device stability
Community radio operators
Run volunteer shows with live DJ mixing
Consistent on-air mixing and playback
Local station hosts
Switch between microphone and music sources
Fewer tools during broadcasts
Show 1 more scenario
Indie streaming producers
Encode and broadcast from a single workstation
Stream control stays local
Encoder configuration is driven from the same desktop workflow used for mixing.
Best for: Fits when small teams run live shows from one machine and need integrated mixing plus streaming.
Jazler RadioStar
enterpriseRadio automation software for music scheduling, commercials, jingles, and broadcast playout.
On-air show logic ties console playout actions to automated scheduling and routing for predictable live programming.
Jazler RadioStar focuses on broadcast console workflows with on-air automation that fits stations already structured around studio roles and live shows. It supports multi-station operation with playlist scheduling, live source switching, and consistent metadata handling for stream outputs.
Engineering control centers on configuring the playout engine, managing encoder targets, and operating reliable audio routing from control room to stream mount points. Automation depth is strongest when event timing, sources, and show logic need to be repeatable across daily programming blocks.
- +Broadcast-consoles-first workflow with tight control of on-air sequencing
- +Repeatable playlist scheduling for daily show blocks and event-driven breaks
- +Multi-station configuration supports shared operational patterns
- +Consistent stream output routing for live sources and automated playout
- –Automation requires careful show and event configuration discipline
- –Extensibility depends on external integration patterns rather than a single unified API surface
- –Operational tuning can take time for complex relay and source switching setups
- –Live studio and stream routing complexity can outgrow simple control rooms
Best for: Fits when radio teams need console-style automation, repeatable show blocks, and controlled stream outputs with minimal operator improvisation.
NextKast
vertical specialistInternet radio automation software for scheduled playback, live shows, and streaming encoders.
API-first automation that lets external systems drive station state, scheduling triggers, and metadata workflows.
NextKast provides an internet radio broadcast workflow that controls the live source chain and on-air automation from a single operator interface. It focuses on listener-facing stream delivery while managing scheduling, metadata updates, and station configuration for consistent playback.
The control surface supports operational tasks like taking sources live, switching feeds, and applying broadcast rules without manual encoder intervention. NextKast also supports integration-oriented deployment patterns through a documented API for automation and external tooling hooks.
- +Central console for source switching and scheduled playback control
- +API surface supports external automation and operational integrations
- +Metadata injection workflow keeps track of artist and title during broadcasts
- +Configuration reuse helps keep multiple shows consistent
- –Automation rules need careful configuration to avoid conflicting schedules
- –Advanced routing scenarios rely on operator discipline during live events
- –Playlist edge cases can require manual intervention for gapless continuity
- –Governance controls are less granular than some broadcaster suites
Best for: Fits when teams need a single operator console plus API-driven automation for scheduled broadcasts.
RadioDJ
SMBFree Windows radio automation software with playlists, scheduling, carts, and encoder integration.
Event-driven scheduling and queue operations in the on-air console for consistent handoffs between DJs.
RadioDJ is a desktop internet radio broadcast console that connects to Icecast or SHOUTcast-style endpoints and controls live automation and DJ playback. It supports playlist management with timing controls, crossfading, and on-air metadata handling so the stream stays consistent during rotating shows.
Operator workflows center on scheduled events and queue operations rather than web-only studio control. RadioDJ is a strong fit when station teams want local control with predictable broadcast behavior and integration into existing streaming infrastructure.
- +DJ console supports scheduling and queue-driven playback for rotating shows.
- +Crossfading controls help maintain smoother transitions between tracks and segments.
- +Metadata injection keeps titles and artist fields aligned with the active play queue.
- +Local desktop workflow reduces latency risk during live interaction.
- –Queue and scheduling require careful operator discipline to avoid gaps during switches.
- –Automation depth is limited compared with full broadcast suites that add newsroom workflows.
- –Multi-studio governance features like strict RBAC are not a core emphasis.
- –External integration options depend on station setup and streaming endpoint compatibility.
Best for: Fits when a small station needs a local DJ console for scheduled playback and controlled on-air metadata.
Liquidsoap
API-firstA scriptable audio and video streaming engine for automated internet radio workflows.
Scripted fallback and live switching graphs that keep the output stream running during source failures.
Liquidsoap turns internet radio workflows into a script-driven pipeline, which differs from visual broadcast consoles. It supports timed playlist scheduling, live source switching, and metadata injection to feed an encoder toward Icecast or Shoutcast.
Its core strength is deterministic automation through declarative configuration that can express crossfades, fallbacks, and stream relay behaviors. Compared with GUI-first tools, Liquidsoap favors versionable config and repeatable runs over drag-and-drop control.
- +Scripted automation for scheduling, crossfades, and fallback logic
- +Programmable live source switching with consistent stream behavior
- +Metadata injection through configuration for track titles and station info
- +Deterministic config makes broadcasts reproducible across deployments
- –Editor UX and debugging are harder than GUI broadcast consoles
- –Operational governance needs external processes for audit and approvals
- –Relies on careful encoder configuration to avoid stream artifacts
- –Not oriented around listener-facing authentication workflows
Best for: Fits when automation-heavy stations need repeatable broadcast logic and config-as-code control.
PlayIt Live
SMBWindows playout software for live assist, scheduled shows, and internet radio automation.
Show workflow automation that coordinates studio actions with scheduled transitions and playlist-driven playback.
PlayIt Live is internet radio broadcast software focused on running a live show workflow from one interface. It combines audio source handling with studio controls, playlist management, and listener facing stream output for consistent on-air operation.
The tool’s automation helps keep transitions predictable when shows rely on scheduled cues and repeatable routines. Admin controls and operational visibility support day-to-day management when multiple contributors share the same broadcast environment.
- +Studio-style controls keep live level changes and transitions in one place
- +Automation supports repeatable show flow with scheduled actions
- +Playlist and cue management reduces manual intervention during broadcasts
- +Operational controls support running sessions with shared responsibilities
- –Advanced workflow customization requires more hands-on configuration time
- –Automation depth is weaker than dedicated automation-first broadcast consoles
- –Integration paths for external systems depend on available connectors and scripts
- –Operational governance features lag tools with built-in fine-grained RBAC
Best for: Fits when one team needs show orchestration, cue scheduling, and stream hosting without a separate broadcast console.
Radiologik
SMBMac radio automation software for scheduled programming, live assist, and internet broadcasting.
Cue-to-playout automation that preserves show timing during scheduled segments and live transitions.
Radiologik delivers internet radio broadcast automation with audio playout, scheduling, and cue-based control for live shows.
It focuses on operational workflows like source control, playlist timing, and continuity around transitions rather than a lightweight browser-only console.
The software supports extensibility through scripting and a documented integration surface for external control and tooling.
It suits stations that need repeatable show execution and administrator-managed operating states.
- +Cue-driven playout helps keep live show timing consistent.
- +Automation can handle scheduled playlists and controlled handoffs.
- +Integration and scripting support external control and custom logic.
- +Operational state management improves repeatable broadcast runs.
- –Control setup requires more planning than console-first radio tools.
- –Advanced workflows depend on scripting familiarity for best results.
- –Queue and scheduling changes can be slower during fast live edits.
- –Integration effort is higher when pairing with custom studio tooling.
Best for: Fits when stations need cue-based automation, controlled transitions, and scripted integration for repeatable live programming.
ZaraRadio
SMBWindows radio automation software for scheduled music, jingles, commercials, and live playout.
Operator console workflows for show control and scheduled playback, designed for predictable on-air operations with minimal setup overhead.
ZaraRadio is an internet radio broadcast software built around managing live on-air workflows and delivering streams to listeners. Core capabilities include an operator console for scheduling and running sessions, encoder configuration for sending audio to an Icecast-style destination, and metadata handling for stream listings.
Automation support covers playlist-style playback control and recurring schedules, while operational tools focus on monitoring and fault recovery during broadcast sessions. Governance and integration depth are limited compared with the top tools in this category, so heavier studio pipelines tend to prefer stronger automation and API surfaces.
- +Clear live console for running shows with predictable control flow
- +Playlist scheduling fits common broadcast rotation needs
- +Encoder configuration supports practical live output setup
- +Metadata updates help listeners and directories show current context
- –Automation and extensibility depth trails Radio.co and SAM Broadcaster
- –API surface for external control and provisioning is limited
- –Governance controls like audit logs and RBAC are thin
- –Advanced studio workflows need careful manual show operations
Best for: Fits when a small station needs a workable show console, scheduling, and stream output control.
Conclusion
After evaluating 10 general knowledge, butt stands out as our overall top pick — it scored highest across our combined criteria of features, ease of use, and value, which is why it sits at #1 in the rankings above.
Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.
How to Choose the Right internet radio broadcast software
This buyer's guide covers the practical mechanics of internet radio broadcast software used to run live streams, automate on-air playlists, and keep listener-facing endpoints stable. The tool set includes butt, Broadwave Streaming Audio Server, Mixxx, Jazler RadioStar, NextKast, RadioDJ, Liquidsoap, PlayIt Live, Radiologik, and ZaraRadio.
Radio.co, RadioDJ, and SAM Broadcaster receive extra focus because they represent common buy decisions around console-driven playback versus server-side or API-driven control.
Internet radio broadcast software for live streaming, automation, and station governance
Internet radio broadcast software is the operational layer that connects an audio source or mixer to listener-facing stream endpoints while managing metadata, scheduling, and transitions. Live stations typically combine a source workflow, an encoder-to-stream path, and an on-air control plane that triggers playback and updates stream-visible titles.
This guide anchors those requirements in butt, which is built around an integrated encoder-to-stream pushing workflow with built-in metadata updates and reconnection logic aimed at keeping the live mount fed. It also contrasts console-driven show control like Jazler RadioStar, where on-air sequencing actions tie directly into automated scheduling and routing so daily show blocks follow a repeatable event model.
Core criteria for internet radio broadcast software: control plane, reliability, automation, and integration
A station’s success depends on the control plane that ties studio actions to listener-facing stream behavior through stable endpoint management and consistent metadata updates. Tools differ sharply in whether they run that control plane inside a console, on a broadcast server, or via API-driven automation.
Reliability features determine whether a live mount stays fed during real-world issues like source disconnects and DJ handoffs. Automation features determine whether daily rotation stays predictable without requiring operator-by-operator improvisation during transitions.
Encoder-to-stream delivery with reconnection and metadata updates
butt connects the live source workflow to stream pushing with built-in metadata updates and reconnection logic aimed at keeping the live mount fed. This focus makes butt fit when listener-visible titles must stay correct without extra glue between the encoder and endpoint.
Server-side endpoint publishing behavior for long-running broadcasts
Broadwave Streaming Audio Server emphasizes server-side stream endpoint management with mount-style publishing behavior for consistent listener-facing endpoints. This model supports stable output when encoder workflow is defined elsewhere and staff focus on endpoints.
Deck-based mixing coupled directly to stream output
Mixxx keeps live mixing and stream output in the same low-latency audio engine so on-air transitions behave consistently during mixing events. This design supports small teams that run shows from one machine.
Console automation that ties show logic to scheduled routing and sequencing
Jazler RadioStar uses on-air show logic that links console playout actions to automated scheduling and routing for predictable programming blocks. Daily show blocks work best when operator actions follow the tool’s show and event model.
API-driven automation that drives station state and scheduled playback
NextKast is built around an API-first automation approach that lets external systems trigger station state, scheduling triggers, and metadata workflows. This makes it a fit when a single operator console needs automation driven by other systems.
DJ console scheduling and queue-driven handoffs with crossfading
RadioDJ provides an on-air console with event-driven scheduling and queue operations to keep handoffs between DJs consistent. Crossfading controls help transitions feel smoother during track and segment changes.
Choose by control philosophy: console show logic, server endpoints, API automation, or scripted fallback
Internet radio broadcast software can be categorized by where automation logic lives. Some tools keep it in a console so scheduling and routing are driven by operator show actions, while others push automation into an API or server process so external systems or endpoint management stay authoritative.
Live operations also require a reliability plan for source failures and transition timing. The right choice depends on whether the station expects operator discipline during switches or prefers scripted fallback graphs that keep output running with minimal hands-on intervention.
Pick a control-plane model: console-first show automation versus API-first station automation
If station workflow centers on console-driven playout actions that must map to repeatable show blocks, Jazler RadioStar is built for that event model. If external systems should drive station state and scheduled playback through an automation surface, NextKast fits because it is API-first and supports operational integrations.
Decide who owns endpoint stability: server endpoints versus pushing from the workstation
If endpoints must be governed as long-running server-side publishing behavior, Broadwave Streaming Audio Server focuses on stream endpoint management so listeners see consistent mount-style endpoints. If the requirement is tight encoder-to-stream pushing with reconnection and metadata updates from the source workflow, butt matches because it integrates stream pushing and metadata correction behavior.
Match the show workflow to how transitions are executed
For a one-machine workflow where deck mixing and stream output must remain consistent during transitions, Mixxx pairs live mixing with direct stream output. For a small station that needs DJ handoffs with queue operations and crossfading controls, RadioDJ centers on an on-air console that supports scheduled playback and smoother segment transitions.
Select the fallback strategy when sources fail during live hours
When scripted fallback and live source switching graphs must keep output running during source failures, Liquidsoap fits because it uses config-as-code automation with scripted fallback and programmable live switching behavior. When cue-to-playout timing preservation is the priority for scheduled segments, Radiologik uses cue-driven automation that keeps show timing consistent even during live transitions.
Use automation depth expectations to prevent operational conflicts
If automation rules are likely to collide with each other during live events, NextKast requires careful configuration because automation rules need discipline to avoid conflicting schedules. If teams expect deep newsroom or multi-workflow operations, console-focused tools like RadioDJ and ZaraRadio can fall behind Radio.co-style automation depth even when scheduling works for straightforward rotations.
Who benefits from these internet radio broadcast tools and why
Stations with reliable live hours care most about how metadata stays correct and how reconnection behavior prevents silence when sources drop. Teams also care whether automation logic is built into the console, exposed through an API, or expressed as scripted fallback graphs.
The right fit depends on staffing patterns and how much operator discipline the broadcast schedule requires during DJ transitions and show blocks.
Small stations running a desktop source workflow for live streaming
butt matches when a desktop source client must keep the live mount fed with built-in reconnection logic and metadata injection updates that keep listener-visible titles current.
Stations that want governed listener-facing endpoints managed as a server process
Broadwave Streaming Audio Server fits when station staff handle encoder workflow elsewhere but need consistent server-side endpoint publishing behavior for long-running broadcasts.
Teams that run live shows from one machine with integrated mixing
Mixxx benefits teams that need deck-based live mixing with direct stream output so on-air transitions share the same low-latency audio engine.
Radio teams that run console-style show blocks with predictable event sequencing
Jazler RadioStar benefits stations that treat the console as the authoritative operator plane because on-air sequencing actions tie directly into automated scheduling and routing for repeatable show blocks.
Engineering-led stations that want external systems to control station state
NextKast suits organizations where scheduling triggers and metadata workflows must be driven by external automation since it offers an API-first automation surface plus a central operator console.
Common pitfalls when buying internet radio broadcast software
Many purchasing mistakes come from assuming that all tools treat automation and reliability the same way. Console-first workflows can require careful operator discipline during queue switches, while API-first or scripted tools shift the burden to configuration clarity and integration logic.
A second mistake is underestimating how much multi-stream routing complexity changes setup effort. Some tools support reliable single-stream workflows but make advanced relay or routing scenarios more manual when station architecture grows.
Choosing a tool for its scheduling features while underestimating the operator discipline required for smooth DJ switches
RadioDJ scheduling and queue operations work best when operators avoid gaps during switchovers, because queue and scheduling require careful discipline to prevent timing breaks.
Assuming server endpoint stability is automatic even when the source workflow disconnects
butt addresses disconnect risk with built-in reconnection logic aimed at keeping the live mount fed, while tools focused on console or server configuration still require a clear reconnection plan in practice.
Over-allocating to built-in automation without checking how it handles schedule conflicts and live routing changes
NextKast can support API-driven automation, but automation rules need careful configuration to avoid conflicting schedules during live events.
Buying a console-centric tool for scripted fallback expectations
Liquidsoap is designed for scripted fallback and live switching graphs, while console-driven suites may not match the same config-as-code reliability approach when sources fail mid-broadcast.
Ignoring the reality that advanced routing and multi-stream relays add setup friction
butt can require manual integration effort for multi-stream relays and complex routing, so stations with that architecture should validate routing complexity early in the selection process.
How We Selected and Ranked These Tools
We evaluated each tool for features that directly affect live playback outcomes, including encoder-to-stream pushing behavior, endpoint stability, and how metadata and reconnection are handled during source issues. Features counted for 40% of the score and we weighted automation and reliability behavior as part of that category.
Ease and value each counted for 30%, which favored tools with less operational friction for day-to-day running and clearer configuration paths. butt separated itself with integrated encoder-to-stream pushing, built-in metadata updates, and reconnection logic aimed at keeping the live mount fed during real disconnects.
Frequently Asked Questions About internet radio broadcast software
Which tool is best when automation must be config-as-code rather than a drag-and-drop console?
How does RadioDJ handle on-air transitions without operator improvisation?
What breaks if encoder reconnection logic fails during a live source outage?
When is an API-first automation approach a better fit than a queue-based desktop console?
Which solution suits stations that already run mixing on one machine and only need controlled stream endpoints?
How do metadata updates behave during rotating content in Radio.co versus SAM Broadcaster?
Which tool is better when a station needs cue-based show timing rather than simple playlist scheduling?
How is live source switching handled in Liquidsoap compared with Jazzler RadioStar?
Which tool is the best match for a small team that wants one interface for show orchestration and streaming output?
Tools reviewed
Primary sources checked during evaluation.
Referenced in the comparison table and product reviews above.
Keep exploring
Comparing two specific tools?
Software Alternatives
See head-to-head software comparisons with feature breakdowns, pricing, and our recommendation for each use case.
Explore software alternatives→In this category
General Knowledge alternatives
See side-by-side comparisons of general knowledge tools and pick the right one for your stack.
Compare general knowledge tools→