GITNUXSOFTWARE ADVICE
Cybersecurity Information SecurityTop 10 Best Magnetic Stripe Reader Software of 2026
Ranked shortlist of magnetic stripe reader software options for deployment and compliance, with tradeoffs and notes on Thales, Entrust, and IDEMIA.
How we ranked these tools
Before any source is gathered, an editor locks the question, what qualifies, and how the piece will be judged.
Search agents gather the source set and the review record, including transcriptions of video reviews and podcasts.
Framework: Features 40% · Ease 30% · Value 30%
Gitnux may earn a commission through links on this page — this does not influence rankings. Editorial policy
Square Point of Sale is the best pick for retail teams that need dependable card-present magstripe capture with minimal reader integration work, whereas ID TECH Universal SDK suits integrators managing mixed ID TECH fleets who want consistent swipe event normalization in POS stacks.
Editor’s top 3 picks
Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.
Square Point of Sale
Tokenized payment handoff from Square Point of Sale keeps store systems out of sensitive card data paths.
Best for: Fits when retail teams need dependable magstripe card-present capture with minimal reader integration work.
ID TECH Universal SDK
Editor pickDevice abstraction layer that standardizes swipe event formatting across ID TECH reader models and connection types.
Best for: Fits when integrators manage mixed ID TECH reader fleets and need consistent swipe event normalization in POS stacks.
MagTek Keyboard Wedge
Editor pickKeyboard wedge emulation that maps decoded swipe output into standard cursor focus and POS input fields.
Best for: Fits when card-present magstripe read data must land in fixed POS fields with minimal app changes.
Comparison Table
Square Point of Sale
SMBPoint-of-sale software that supports magnetic stripe card readers for payment acceptance.
Tokenized payment handoff from Square Point of Sale keeps store systems out of sensitive card data paths.
Square Point of Sale fits teams that want magstripe capture without building a POS middleware layer around an MSR SDK. The device and software integration route swipe data into Square’s payment flow for authorization and settlement, which reduces integration surface compared with RS-232, OPOS, or JavaPOS-style reader integrations. The tradeoff is less visibility into parsed track fields and limited extraction of raw track data for internal verification or evidence workflows.
A common fit is retail checkout where staff need quick, consistent swipe handling and reversal handling during line downtime. In that setting, centralized staff permissions and location-level configuration help reduce procedural drift across registers. Magstripe edge cases like unreadable swipes or partially read tracks are handled by Square’s processing and decline behavior rather than by exposing low-level track decoding controls.
- +Integrated payment flow for swipes without POS middleware plumbing
- +Centralized staff permissions for multi-register operations
- +Tokenized handoff reduces scope of cardholder data exposure
- +Consistent reader experience across supported Square terminals
- –Limited access to parsed track outputs and raw track material
- –Magstripe-specific customization is constrained by the integrated processing path
Store operations teams
Daily checkout swipe handling
Fewer checkout handling variations
Regional retail managers
Multi-location staff access control
Lower risk of unauthorized actions
Show 1 more scenario
Internal audit and compliance leads
Reduce card data handling scope
Smaller PCI-DSS handling surface
Tokenization limits where PAN-like data is visible inside store systems that run POS actions.
Best for: Fits when retail teams need dependable magstripe card-present capture with minimal reader integration work.
ID TECH Universal SDK
API-firstDeveloper toolkit for ID TECH readers that supports magnetic stripe data capture and device integration.
Device abstraction layer that standardizes swipe event formatting across ID TECH reader models and connection types.
ID TECH Universal SDK fits merchants and integrators who need predictable swipe event behavior across ID TECH reader models in POS middleware and checkout stacks. The core capability is converting device-origin swipe reads into normalized host events that application code can consume consistently. Bidirectional swipe parsing and track handling work at the device-integration layer, which reduces per-model branching in application logic. Configuration controls also support operational tuning for multi-device deployments.
A clear tradeoff is that the SDK integration surface can require careful configuration when reader hardware, connection type, and output expectations differ by site. It fits teams that need a single integration path to standardize card-present workflows across stores while controlling error handling and event formatting. It also fits environments where swipe reversal handling must be mapped into existing POS middleware logic.
- +Normalized swipe events reduce per-model logic in POS middleware
- +Device abstraction supports mixed deployment of ID TECH reader models
- +Configuration options help standardize behavior across sites
- +Host-side handling streamlines mapping into keyboard or POS pipelines
- –Integration effort rises when connection types and output formats vary
- –Operational tuning takes iteration for consistent store-level behavior
- –Advanced behaviors depend on correct reader and host configuration
- –Testing overhead increases when handling reversal and partial reads
POS middleware teams
Standardize swipe events across stores
Fewer integration variations per store
System integrators
Unify multi-model reader deployments
Lower project customization overhead
Show 2 more scenarios
Retail IT operations
Tune reader behavior consistently
More consistent operational reads
Uses configuration controls to align swipe outcomes and error handling across locations.
Checkout application developers
Map swipe data into existing flows
Cleaner application event handling
Converts swipe events into application-ready data structures for card-present verification.
Best for: Fits when integrators manage mixed ID TECH reader fleets and need consistent swipe event normalization in POS stacks.
MagTek Keyboard Wedge
vertical specialistKeyboard wedge utility software for MagTek magnetic stripe readers that outputs card data into any text field.
Keyboard wedge emulation that maps decoded swipe output into standard cursor focus and POS input fields.
MagTek Keyboard Wedge is aimed at environments where the POS or middleware expects keystrokes or field-populated input rather than a device API call. Configuration-driven output formatting helps normalize track data for the target application. It also includes device-side abstractions so host applications can treat the reader like a keyboard input source.
A common tradeoff is that field-population via keyboard behavior limits how much metadata other than the formatted swipe string can be carried into the application. It fits situations where the POS UI flow is already locked down and adding a new MSR SDK or OPOS service object path would require larger certification effort.
- +Keyboard wedge emulation reduces POS integration changes
- +Configurable output formatting targets fixed field requirements
- +Supports HID POS style input for common POS workflows
- +Works with existing UI flows that accept typed data
- –Limited programmatic context compared with device APIs
- –Requires careful host field mapping to avoid parsing mismatches
- –Track reversal handling depends on configuration and host tolerance
- –Harder to integrate when the POS lacks keyboard input support
Retail POS integration teams
Route swipe data into existing fields
Reduces code changes and recertification scope
Legacy application owners
Use without MSR SDK integration
Avoids rewriting card parsing modules
Show 2 more scenarios
Store operations IT
Standardize decoding across terminals
Improves data consistency for disputes
Applies consistent decoding and formatting so terminal outputs match downstream expectations.
Payment middleware maintainers
Feed POS middleware from typed input
Simplifies middleware ingestion logic
Uses configured output strings so middleware receives deterministic swipe payloads from the UI layer.
Best for: Fits when card-present magstripe read data must land in fixed POS fields with minimal app changes.
Dynamag Utilities
vertical specialistConfiguration and test software for Dynamag magnetic stripe card readers and swipe devices.
Configurable keyboard wedge emulation that maps decoded fields into POS-ready input for legacy terminals.
Dynamag Utilities packages magnetic stripe reader software into a device-focused bundle for swipe decoding, validation, and host output. It targets integration paths that rely on serial or HID-style POS workflows, including configurable keyboard wedge emulation and structured output formats for downstream verification.
- +Configuration-driven swipe parsing reduces custom middleware changes
- +Supports multiple host output styles like keyboard wedge and serial
- +Per-track handling helps isolate decoding failures to specific tracks
- +Validation-oriented formatting supports consistent downstream verification inputs
- –Throughput tuning depends on device driver behavior and OS USB or serial stack
- –Advanced governance features like RBAC and audit log are limited for larger fleets
- –Raw track extraction coverage can be inconsistent across reader models
- –Integration requires disciplined deployment setup across each reader endpoint
Best for: Fits when a technical team needs swipe decoding plus POS-style output without building custom drivers.
Toast POS
vertical specialistRestaurant POS software that connects to payment reader hardware for card-present transactions.
Checkout and reconciliation are built around Toast POS orders, refunds, and shift close so swipe acceptance is transaction-stateful.
Toast POS records card-present workflows in-store and supports magstripe use through its integrated payment and device stack. Toast POS routes transactions into its POS-led ordering and reconciliation flow, so swipe data reaches checkout rather than staying inside a standalone reader tool.
- +Checkout-linked workflow reduces reconciliation gaps between order and payment
- +User permissions apply inside the same system that manages refunds and voids
- +Shift-close reporting consolidates sales and card payments for operations
- +Device integration limits custom middleware work for magstripe acceptance
- –Magstripe parsing and raw track access are not the primary exposed capability
- –Integration depth depends on approved payment hardware and POS device mapping
- –Workflow automation and API-driven checkout events are limited for MSR-level use cases
- –Error handling and swipe reversal behavior are constrained by the payment stack
Best for: Fits when magstripe needs to feed POS checkout state and reporting with minimal custom integration.
SwipeSimple
SMBSwipeSimple provides merchant payment software with card readers that support magnetic-stripe transactions.
Configurable magstripe parsing output that can present decoded results in POS-friendly keyboard wedge style.
SwipeSimple fits teams that need magnetic stripe capture and parsing across POS hardware without relying on custom reader firmware changes. It provides keyboard wedge and serial style output options for magstripe data routing into existing applications, plus configurable track decoding behaviors for common formats.
- +Keyboard wedge style input reduces POS integration changes
- +Track parsing configuration helps normalize decoded outputs
- +Reader-to-application mapping supports mixed device deployments
- +Local parsing avoids pushing full raw swipes downstream
- –API surface is limited for programmatic swipe ingestion at scale
- –Some advanced workflows depend on device-specific setup
- –Error handling knobs can be harder to validate end to end
- –Throughput tuning is constrained by the reader interface mode
Best for: Fits when POS or middleware expects device-like magstripe input and teams need configurable track decoding.
PayJunction
SMBPayJunction provides payment software and card-present readers for magnetic-stripe and other transaction types.
Configurable swipe handling and output shaping built for downstream payment middleware ingestion.
PayJunction focuses on integrating magnetic stripe reading into existing payment and POS environments, with software meant to sit beside card-present workflows. The core capability is reliable magstripe parsing that produces structured track data outputs for downstream payment logic.
- +Structured track output reduces custom parsing code in downstream services
- +Supports practical swipe behaviors for real-world counter errors
- +Integration-oriented configuration fits payment middleware flows
- +Clear separation between reader input handling and payment verification steps
- –Requires integration work to match specific terminal or OS device layers
- –Limited visibility into raw swipe artifacts for deeper troubleshooting
- –Setup complexity increases when multiple reader models must be mapped
- –Error handling behavior can be less granular during partial-read events
Best for: Fits when a merchant acquirer or POS middleware needs predictable magstripe track handling with controlled deployment.
CardPointe
enterpriseCardPointe provides merchant payment software, terminals, and card-present transaction processing.
Heartland-oriented capture configuration that keeps device integration and payment routing aligned for card-present processing.
CardPointe is a card-present payment capture offering from Heartland that integrates card reader hardware into payment processing workflows. It focuses on Magstripe and POS-style capture paths with terminal-facing device integration patterns such as RS-232 and USB HID POS protocols.
- +Built for card-present payment capture workflows tied to an acquirer integration
- +Supports common POS device connection patterns like RS-232 and USB HID
- +Includes card-present verification flow handling for capture-time risk controls
- +Configurable device and gateway setup for reader deployment across locations
- –Magstripe parsing behavior depends on connected terminal and reader configuration
- –Operational tuning can require payment-processor alignment beyond reader software
- –Limited visibility into raw track recovery outcomes for detailed dispute evidence
- –Automation and API surface are narrower than general-purpose MSR middleware
Best for: Fits when payment operations need card-present capture tightly aligned to an acquirer workflow.
Payanywhere
SMBPayanywhere provides merchant payment software and card readers for in-person transactions.
Reader capture-to-payment workflow mapping that treats track parsing as part of the acquiring integration path.
Payanywhere’s magnetic stripe reader software is designed for card-present capture to flow into payment processing rather than to act as a standalone decoding library. Track handling focuses on producing payment-ready fields from swipes so POS and terminal middleware can continue the authorization path.
- +Built around card-present capture flows that map cleanly to acquiring processing
- +Track data handling supports typical POS decoding paths for payment field extraction
- +Integration focus reduces custom glue between the reader output and payment gateway input
- +Works best when reader activity is already managed by a compatible terminal workflow
- –Less control over low-level decode and error handling compared with SDK-first MSR engines
- –Complex reader fleet behavior relies on the surrounding Payanywhere deployment tooling
- –Limited visibility into raw parsing details for forensic dispute evidence workflows
- –Hardware compatibility depends on the supported terminal and integration model
Best for: Fits when reader capture must plug into an existing Payanywhere payment workflow with minimal custom parsing logic.
Clover
SMBClover provides point-of-sale software and card readers that support swipe, chip, and contactless payments.
End-to-end swipe-to-authorization handling that ties decoded track data to Clover payment routing without separate POS middleware integration.
Clover is a magnetic stripe reader software offering tied to Clover devices and payment workflows rather than a standalone MSR SDK library. Clover’s card-present flow centers on swipe capture, track decoding, and payment authorization handoff inside its POS and payments stack.
- +Card-present swipe to authorization workflow stays inside one device ecosystem
- +Consistent POS-side handling reduces integration surface for MSR parsing errors
- +Device attachment and JavaPOS-style mapping are not required for Clover-linked hardware
- +Operational logging aligns to merchant payment troubleshooting workflows
- –Limited control over raw track data extraction compared with dedicated reader SDKs
- –Extensibility for custom magstripe parsing formats is constrained by Clover workflow
- –Track error correction parity and swipe reversal behavior are not user-tunable
- –Non-Clover device driver abstraction and RS-232 style integration require extra integration work
Best for: Fits when swipe capture and payment authorization can stay within a Clover device and POS workflow.
Conclusion
After evaluating 10 magnetic stripe reader software, Square Point of Sale 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 Magnetic Stripe Reader Software
Magnetic stripe reader software fits between the swipe hardware and the POS or payment workflow by decoding track data into usable inputs. This buyer's guide covers Square Point of Sale, ID TECH Universal SDK, MagTek Keyboard Wedge, Dynamag Utilities, Toast POS, SwipeSimple, PayJunction, CardPointe, Payanywhere, and Clover.
The deciding factor is how each tool handles integration depth, from keyboard wedge emulation and device abstraction to the point where tokenization or authorization takes over. Readers can compare which systems expose decoded track outputs and which keep parsing inside a store or payment ecosystem.
Magnetic Stripe Reader Software for decoding and routing track data into POS workflows
Magnetic stripe reader software captures card-present swipes and converts track 1 and track 2 data into structured fields or POS-ready inputs. Some tools focus on decoding and output shaping, like MagTek Keyboard Wedge mapping decoded swipe content into standard cursor-focused fields.
Other tools combine swipe handling with a broader payment workflow so staff permissions, checkout, and reconciliation align with the swipe that started the transaction. Square Point of Sale, for example, emphasizes tokenized payment handoff so store systems avoid sensitive card data paths while still processing swipes through the Square stack.
Integration depth and automation surface for magstripe decoding and POS handoff
Magnetic stripe reader software succeeds when decoded track data lands in the POS workflow through a predictable integration path, not through ad hoc parsing in every store system. Integration depth shows up in how keyboard wedge emulation, device abstraction, or payment ecosystem handoff reduces or increases the middleware work needed to accept swipes consistently.
Capture-to-payment workflow coupling versus parser-only integration
Square Point of Sale and Clover tie decoded swipe handling to authorization and payment routing inside their ecosystems. CardPointe and Payanywhere keep the capture path aligned with acquirer workflows while still requiring careful device configuration to get consistent decode behavior.
Keyboard wedge emulation for fixed POS field ingestion
MagTek Keyboard Wedge and Dynamag Utilities map decoded swipe output into standard cursor-focused input fields for legacy terminals. SwipeSimple also provides configurable keyboard wedge style output for POS or middleware systems that expect device-like input.
Device abstraction and normalized swipe events across reader models
ID TECH Universal SDK standardizes swipe event formatting across ID TECH reader models and connection types. This approach reduces per-model logic in POS middleware compared with tools that push teams toward per-device output shaping.
Access to parsed fields versus raw track material for troubleshooting
Square Point of Sale emphasizes tokenized payment handoff and therefore limits direct access to parsed track outputs and raw track material. MagTek Keyboard Wedge and Dynamag Utilities focus on output mapping for host fields, which can leave deeper decode inspection to the connected device or driver layer.
Output shaping and error-tolerant swipe handling for counter errors
PayJunction provides structured track output designed for downstream payment middleware ingestion and supports practical swipe behaviors for real-world counter errors. SwipeSimple and Dynamag Utilities rely on configuration-driven decoding and output presentation, so handling edge cases depends on how each configuration is tuned to the host expectations.
Fleet governance controls for multi-register operations
Square Point of Sale uses centralized staff permissions for multi-register operations inside the same system that manages refunds and voids. Dynamag Utilities notes limited advanced governance features like RBAC and audit log, which matters when larger fleets need centralized change control.
Choose by integration contract: wedge input, normalized events, or ecosystem handoff
Selection turns on the integration contract the POS stack already supports. Some deployments need keyboard wedge style input because the terminal app expects cursor-driven entry, while others need normalized swipe events because middleware routes transactions through services that cannot easily consume raw key events.
Map the POS ingestion mode to keyboard wedge versus programmatic events
If the POS app can only accept characters into fixed fields, MagTek Keyboard Wedge and Dynamag Utilities provide keyboard wedge emulation that targets host cursor focus. If the POS middleware expects structured swipe events across mixed reader models, ID TECH Universal SDK normalizes swipe event formatting to reduce per-model parsing logic.
Decide where swipe parsing responsibility lives in the transaction
If the swipe needs to stay inside a single checkout and reconciliation system, Square Point of Sale and Clover keep the workflow transaction-stateful around authorization and payment routing. If the environment must feed an external acquirer or middleware path, CardPointe and Payanywhere emphasize capture workflows that align with acquiring processing and require device configuration discipline.
Validate how much low-level trace data is available for exception handling
If troubleshooting requires visibility into raw track material, reader SDK and driver stacks matter, and Square Point of Sale explicitly limits access to parsed track outputs and raw track material. If exception handling can rely on host-level outcomes and normalized event data, keyboard wedge tools and device abstraction layers can reduce host integration complexity.
Test integration against mixed connection types and deployment realities
For deployments with mixed reader connections, ID TECH Universal SDK includes a device abstraction layer that standardizes swipe event formatting across connection types. For environments that rely on serial or USB HID device patterns, CardPointe and keyboard wedge tools can fit, but integration effort rises when output formats vary across OS and driver stacks.
Confirm governance and configuration management for multi-register scale
If the organization needs centralized control tied to staff operations, Square Point of Sale includes centralized staff permissions for multi-register workflows. If the fleet depends on RBAC and audit log for configuration changes, Dynamag Utilities limits advanced governance features like RBAC and audit log and may require supplemental process controls.
Who should buy Magnetic Stripe Reader Software
Magnetic stripe reader software fits teams that must convert card-present swipe input into fields or events that a POS or payment workflow can consume reliably. The right choice depends on whether the store stack expects keyboard wedge input, normalized swipe events, or a workflow tied to tokenization and authorization.
Retail operators running multi-register stores with centralized staff permissions needs
Square Point of Sale supports multi-register operations with centralized staff permissions and processes swipes through an integrated payment flow. This reduces the need for POS middleware plumbing and limits sensitive card data exposure in store systems.
Integrators with mixed ID TECH reader models and multiple connection types to normalize
ID TECH Universal SDK standardizes swipe event formatting across ID TECH reader models and connection types. This lets POS middleware apply one normalization path instead of maintaining per-model logic.
Merchants modernizing legacy terminals that accept input as keystrokes
MagTek Keyboard Wedge and Dynamag Utilities map decoded swipe data into standard cursor-focused fields. This helps teams avoid modifying POS apps that expect data entry in fixed input controls.
Payment operations teams aligning reader capture to an acquiring workflow
CardPointe is built for card-present capture workflows aligned with an acquirer integration and supports common POS device connection patterns. Payanywhere also treats reader capture-to-payment workflow mapping as part of the acquiring path.
Teams that need configurable swipe decoding output shaping without custom driver development
Dynamag Utilities and SwipeSimple provide configuration-driven parsing and POS-ready output styles that can reduce custom middleware changes. This fits deployments where configuration controls the decode and output presentation more than code changes.
Common pitfalls when buying Magnetic Stripe Reader Software
Buying mistakes usually come from mismatched integration contracts and underestimated exception handling requirements. Keyboard wedge output and normalized swipe events behave differently under misreads, swipe reversals, and terminal-specific field mapping constraints.
Choosing a keyboard wedge tool when the POS stack needs programmatic swipe event ingestion
MagTek Keyboard Wedge and Dynamag Utilities focus on cursor-focused character input fields rather than middleware-native event ingestion. Teams with middleware that expects structured swipe events are better served by ID TECH Universal SDK normalized swipe events.
Assuming end-to-end swipe authorization implies access to raw track artifacts for troubleshooting
Square Point of Sale emphasizes tokenized payment handoff and limits access to parsed track outputs and raw track material. Reader-first integration paths are needed when deep decode inspection drives dispute evidence and troubleshooting.
Underestimating host field mapping requirements for fixed POS input positions
MagTek Keyboard Wedge requires careful host field mapping to avoid parsing mismatches because it emulates keyboard wedge behavior into POS input fields. Dynamag Utilities is configurable for multiple host output styles, but throughput and tuning still depend on the OS USB or serial stack and the device driver behavior.
Treating integration tuning as a one-time setup across a reader fleet
ID TECH Universal SDK reduces per-model logic but integration effort still rises when connection types and output formats vary across the fleet. PayJunction notes that integration work is required to match specific terminal or OS device layers, so store-level validation prevents inconsistent swipe handling.
Buying a reader-focused tool without aligning with the surrounding payment workflow state
CardPointe and Payanywhere align capture to acquirer workflow paths, but magstripe parsing behavior depends on connected terminal and reader configuration. Clover keeps swipe authorization within its device ecosystem, so bypassing that workflow path can reintroduce integration complexity.
How We Selected and Ranked These Tools
We evaluated integration depth by checking whether each tool fits keyboard wedge input, device abstraction with normalized swipe events, or an ecosystem path that ties swipe handling to authorization and reconciliation. Features represented 40% of the scoring because swipe output shaping, device behavior consistency, and workflow coupling determine whether card-present swipes work in real store conditions.
Ease and value each represented 30% because configuration effort for deployment and the operational overhead of maintaining integration paths across registers affects day-to-day performance. Square Point of Sale separated itself by combining swipe acceptance inside checkout workflows with tokenized payment handoff, which reduces store systems exposure to sensitive card data paths while still supporting multi-register operations with centralized staff permissions.
Frequently Asked Questions About Magnetic Stripe Reader Software
How do Square Point of Sale and Payanywhere route magstripe data into payment workflows without exposing raw tracks to the POS layer?
When should integration teams choose ID TECH Universal SDK instead of MagTek Keyboard Wedge for bidirectional swipe parsing needs?
What breaks if a deployment relies on keyboard wedge behavior but the selected software expects serial-style output?
How do SwipeSimple and Clover differ in how decoded track data connects to downstream authorization?
Which tool offers the most direct device abstraction layer for consistent swipe event formatting across multiple reader models?
When do operations teams need admin controls tied to shift close and reconciliation rather than reader-parser configuration?
How does raw track data extraction differ between Payanywhere and Clover from an integration design perspective?
Which software handles card-present verification and acquirer-aligned routing format requirements closer to the device integration layer?
What tradeoff occurs when a team selects a POS-integrated approach like Square Point of Sale or Toast POS instead of a reader-parser focused workflow like Dynamag Utilities?
Tools reviewed
Primary sources checked during evaluation.
Referenced in the comparison table and product reviews above.
Funding and competing interests
This study was co-funded by several of the vendors assessed in it. No single vendor funded it. Funders could propose the market studied.
They had no role in selecting vendors, setting or weighting criteria, analysing data or drawing conclusions, and they received the same factual-accuracy check as every other vendor assessed.
Market definition, inclusion rules and criteria weights were fixed by an editor before research began and did not change afterwards. Editorial process →
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
Cybersecurity Information Security alternatives
See side-by-side comparisons of cybersecurity information security tools and pick the right one for your stack.
Compare cybersecurity information security tools→