How to use the Text Character Limit Splitter.
Splitting text should respect the actual limit definition and preserve order. Characters, code points and bytes are different measures.
Make the workflow fit your task.
Define the limit as bytes, code points or another platform-specific count. Split at suitable boundaries while preserving order and accounting for labels or separators. Report each chunk's measured size and flag any single word that exceeds the limit.
- What you provide
- Text, limit and required continuation markers.
- What you get
- Ordered chunks preserving words and code-point-aware limits.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Text: red blue green; maximum chunk length 8 characters; keep words intact.
Completed example
Chunk 1: red blue. Chunk 2: green. Include separators or continuation markers in the count if required.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Should continuation labels count toward the chunk limit?
Yes, if they are sent as part of the chunk. Reserve their space before choosing split points.
Why does a chunk fit a character limit but exceed a byte limit?
Some characters require multiple bytes in UTF-8. Count using the destination's actual measure instead of visible length.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑