> ## Documentation Index
> Fetch the complete documentation index at: https://www.helius.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Solana Transaction Sending

> Choose the right way to send Solana transactions with Helius. Compare basic sending for apps and wallets against high-performance sending for traders.

## Why is transaction sending hard on Solana?

Every interaction with Solana — trading on a DEX, minting an NFT, transferring tokens, or calling a program — requires a transaction that lands onchain. During network congestion, unoptimized transactions are frequently dropped before reaching a leader. Helius provides direct routing to leaders, priority fee optimization, and enterprise-grade redundancy so your transactions confirm quickly and reliably.

This page helps you choose the right sending method for your use case. There are two paths:

<CardGroup cols={2}>
  <Card title="Basic sending" icon="shield-check" href="#basic-sending">
    For apps where reliability matters more than raw speed — payments, wallets,
    social apps, and most program interactions. Billed per send from your plan's
    credits.
  </Card>

  <Card title="High-performance sending" icon="rocket" href="#high-performance-sending">
    For latency-sensitive trading — propAMMs, snipers, copy traders, liquidation
    bots, arbitrage. Routed through [Helius Sender](/sending-transactions/sender)
    and paid for with SOL tips instead of credits.
  </Card>
</CardGroup>

## Which option should I choose?

Start with the question that matters most: **is latency critical to your business?**

| Your use case                                                             | Recommended method                                               | Cost model                              |
| ------------------------------------------------------------------------- | ---------------------------------------------------------------- | --------------------------------------- |
| Payments, wallets, social apps, general program calls                     | [Basic `sendTransaction`](/sending-transactions/send-manually)   | 1 credit per send                       |
| Atomic, all-or-nothing execution (no latency requirement)                 | [Basic `sendBundle`](/sending-transactions/send-bundle)          | 1 credit per send                       |
| Competitive trading needing the fastest landing (transactions or bundles) | [Sender Max](/sending-transactions/sender-max)                   | 0.001 SOL min tip (priority tip buffer) |
| Atomic, all-or-nothing execution with the fastest landing                 | [Sender Max — bundles](/sending-transactions/sender-max#bundles) | 0.001 SOL min tip (priority tip buffer) |
| Cost-optimized trading on a single fast path                              | [Sender — SWQOS-only](/sending-transactions/sender-swqos-only)   | 0.000005 SOL min tip                    |

<Tip>
  Not sure? If you are building a wallet, payment flow, or general app, start
  with **basic sending**. If you are competing to land trades ahead of
  others, use **Helius Sender**.
</Tip>

## Basic sending

Basic sending is the right choice when reliability matters more than shaving off milliseconds. Transactions route directly to current and upcoming block leaders through a priority lane, bypassing the public queue. Each send is billed as **1 credit** from your plan.

<CardGroup cols={2}>
  <Card title="Send transactions" icon="paper-plane" href="/sending-transactions/send-manually">
    Build, optimize, and confirm a `sendTransaction` with compute-unit
    tuning, priority fees, and a robust confirmation loop.
  </Card>

  <Card title="Send bundles" icon="layer-group" href="/sending-transactions/send-bundle">
    Submit up to 5 transactions for atomic, all-or-nothing execution via
    `sendBundle`, proxied directly to Jito.
  </Card>
</CardGroup>

<Note>
  Basic sending is most appropriate when latency is not critical to your
  business (payments, wallets, social apps, and similar). For the lowest possible
  latency, use [Helius Sender](#high-performance-sending).
</Note>

## High-performance sending

For latency-sensitive trading, [Helius Sender](/sending-transactions/sender) submits your transaction across all pathways (Helius, Jito, Harmonic, Rakurai, etc.) for the fastest possible inclusion. Sender **does not consume API credits** — you pay with a SOL tip on each transaction, and it is available on every plan including the free tier.

Sender offers two tiers. Pick based on how competitive your transactions need to be:

<CardGroup cols={2}>
  <Card title="Sender Max (fastest landing)" icon="trophy" href="/sending-transactions/sender-max">
    Routed across every high-speed pathway and entered into a priority tip
    buffer, with a minimum **0.001 SOL** tip. Handles both transactions and
    bundles — best for highly contested submissions.
  </Card>

  <Card title="SWQOS-only (cost-optimized)" icon="dollar-sign" href="/sending-transactions/sender-swqos-only">
    Routes through a single fast SWQOS path with a minimum **0.000005 SOL** tip.
    Best when you want low-latency sending at the lowest tip.
  </Card>
</CardGroup>

<Tip>
  Building a trading strategy? The [Trading](/trading/overview) section covers the
  full toolkit — including [Pre Confirmations](/pre-confirmations/overview) for
  the earliest transaction signals.
</Tip>

## Key concepts for reliable transactions

Regardless of the method you choose, understanding these concepts is key to success on Solana.

<Card title="Optimizing Transactions" icon="gauge-high" href="/sending-transactions/optimizing-transactions">
  Learn best practices for setting priority fees and compute units to maximize
  your transaction's chances of landing quickly.
</Card>