1---
2title: Token-2022 (Token Extensions)
3description: Kit-compatible @solana-program/token-2022 client — key differences from base Token program, account sizing, ATA derivation, and extension reference.
4---
5 
6# Token-2022 (Token Extensions)
7 
8Program address: `TokenzQdBNbLqP5VEhdkAS6EPFLC1PHnBqCXEpPxuEb`
9 
10```ts
11import { TOKEN_2022_PROGRAM_ADDRESS } from '@solana-program/token-2022';
12```
13 
14Token-2022 extends the base Token program with configurable extensions. For a full guide to available extensions and their use cases, see the [Token Extensions documentation](https://solana.com/docs/tokens/extensions).
15 
16## When to Use Token-2022 vs Token
17 
18| Use Token-2022 | Use Token |
19|----------------|-----------|
20| Transfer fees needed | Simple fungible tokens |
21| On-chain metadata | Maximum compatibility |
22| Confidential transfers | Lowest compute cost |
23| Transfer hooks | Existing ecosystem integration |
24| Interest-bearing tokens | |
25| Non-transferable tokens | |
26 
27## Key Differences from Base Token
28 
29### Variable Account Sizes
30 
31Unlike base Token (fixed 82/165 byte accounts), Token-2022 sizes vary by extension. Calculate before creating or rent allocation fails:
32 
33```ts
34import { getMintSize, getTokenSize } from '@solana-program/token-2022';
35 
36// Without extensions
37const baseSize = getMintSize(); // 82 bytes
38 
39// With extensions - pass extension configs
40const sizeWithExtensions = getMintSize([
41  { extension: 'TransferFeeConfig', ... },
42  { extension: 'MetadataPointer', ... },
43]);
44```
45 
46### ATA Derivation
47 
48Same pattern as base Token, but you **must** pass `TOKEN_2022_PROGRAM_ADDRESS` — using the wrong program address derives the wrong ATA.
49 
50```ts
51import { findAssociatedTokenPda, TOKEN_2022_PROGRAM_ADDRESS } from '@solana-program/token-2022';
52 
53const [ata] = await findAssociatedTokenPda({
54  owner: walletAddress,
55  mint: mintAddress,
56  tokenProgram: TOKEN_2022_PROGRAM_ADDRESS,
57});
58```
59 
60### Extension Initialization Order
61 
62Extension instructions must come **before** mint initialization — the runtime processes them in order and mint init finalizes the account.
63 
64### Account Fetching
65 
66Same patterns as base Token — extensions are accessible via `mint.data.extensions`:
67 
68```ts
69import { fetchMint, fetchToken } from '@solana-program/token-2022';
70 
71const mint = await fetchMint(rpc, mintAddress);
72// Access extensions via mint.data.extensions
73```
74 
75## Extensions Reference
76 
77See [Token Extensions documentation](https://solana.com/docs/tokens/extensions) for implementation details on each extension.
78