> ## 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.

# Log Truncation & Untruncated Log Streaming

> LaserStream truncates transaction log messages to 10 KB by default for better speed and performance. Stream full, untruncated logs with the dedicated untruncated endpoints.

By default, LaserStream truncates transaction log messages to **10 KB** for better speed and performance. Smaller messages mean lower bandwidth usage and lower latency for every consumer, and most transactions produce logs well under this limit.

If your use case depends on complete logs — for example, parsing program logs for events or indexing verbose CPI-heavy transactions — connect to a dedicated untruncated endpoint instead.

## Untruncated Endpoints

These endpoints stream full, untruncated transaction log messages:

| Region  | Location                   | Endpoint                                                     |
| ------- | -------------------------- | ------------------------------------------------------------ |
| **ewr** | Newark, NJ (near New York) | `https://laserstream-mainnet-ewr-untruncated.helius-rpc.com` |
| **fra** | Frankfurt, Europe          | `https://laserstream-mainnet-fra-untruncated.helius-rpc.com` |

They use the same API keys, subscribe requests, and clients as the [standard endpoints](/laserstream/grpc#mainnet-endpoints) — log messages are simply not truncated. One limitation: [historical replay](/laserstream/historical-replay) is not currently supported on the untruncated endpoints.

To switch, point your client at the untruncated URL:

```typescript index.ts theme={"system"}
import { subscribe, CommitmentLevel, LaserstreamConfig, SubscribeRequest } from 'helius-laserstream';

const config: LaserstreamConfig = {
  apiKey: 'YOUR_API_KEY',
  endpoint: 'https://laserstream-mainnet-ewr-untruncated.helius-rpc.com', // Untruncated logs
};
```

## Choosing an Endpoint

* **Standard endpoints** (default): best for most workloads. Truncated logs keep messages small, which reduces bandwidth and latency.
* **Untruncated endpoints**: use when you need complete transaction logs and can accept the larger message sizes that come with them. Not compatible with historical replay for now.