> For the complete documentation index, see [llms.txt](https://docs.wlth.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wlth.xyz/investment/slices/splitting-slices.md).

# Splitting Slices

**What does splitting mean?**\
A Slice is your tokenised share of a fund or deal. With WLTH, you can split a Slice into smaller units, each one independently tradable and still tied to its share of the original investment.

* Each new Slice keeps its proportional value of the fund.
* The minimum size for a new Slice is **$20–$50**.
* As the value of the fund changes, the value of each Slice changes with it.

***

### How to Split a Slice

1. Log in to the WLTH app with the wallet holding your Slice.
2. Go to **Portfolio** → find the fund and Slice you want to split.
3. Click **Split**.
4. Choose how many new Slices you want:
   * Default = equal amounts
   * Or select **Custom** and enter your own values in $.
5. Click **Continue**, then sign the transaction in your wallet.

✅ The new Slices will now appear in your wallet.

***

### Important Notes

* Once a Slice is split, it **cannot be merged back together**.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.wlth.xyz/investment/slices/splitting-slices.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.