If the question lives in months or years of messages, you need a text message history analyzer, not five lines taken out of sequence.
If you want to analyze text message history, the important question is not just whether a tool accepts a big file. It is whether the product can preserve timing, sequence, repair attempts, pursuit-withdraw loops, and drift across months or years of texts without pretending one model saw everything at once. Grey Mirror is designed around that larger-context job.
- supported upload ceiling for a single exported conversation file
- 500MB
- maximum messages accepted before the parser truncates the history
- 500,000
- large uploads may take longer, but countable metric totals should not be thinned
- Full-fidelity counts
File size is not the same thing as analytical depth
A tool can let you upload a large export and still only reason over a thin slice of it. What matters is whether the product preserves the timeline and turns the thread into stable pattern measurements.
Long context changes the answer
Repair failure, response-time drift, breadcrumbing, delayed accountability, and collapsing warmth usually become obvious only when the thread stays in sequence over time.
Full-thread capacity matters
Grey Mirror can accept very large histories, and the tradeoff is time rather than thinner metric counts. Huge exports should show a clear processing state while the pipeline batches work and preserves the countable timeline.
What “large context” means in Grey Mirror
Grey Mirror is built for exported conversations, zipped message archives, and long-running threads where the answer depends on what happened before and after the most dramatic moment. The public product capacity is substantial: the upload workflow accepts files up to 500MB, and the parser can ingest up to 500,000 messages before safety truncation.
That matters because long-thread relationship analysis is not just an NLP token question. It is a sequence question. You want the thread to preserve who initiated, who withdrew, when the pacing changed, whether repair landed, and whether a dynamic improved or degraded over time.
- Built for exported conversations, not only screenshots
- Useful for months or years of relationship history
- Preserves participant turns and timing context
- Lets one report compare early and late phases of the same relationship
Why long message threads reveal what short excerpts hide
Short excerpts are often enough for a red-flag triage question. They are weaker for questions like “who is carrying the repair,” “when did the reply pattern change,” “does this ex always reappear after silence,” or “is warmth still real or only occasional.” Those are long-context questions.
When someone asks for a large-context text analyzer, they are usually asking for pattern memory: the ability to compare earlier windows to later windows, detect cycles, and tell whether one reassuring message is part of real change or just another loop in a familiar pattern.
- Pursuit-withdraw loops need multiple turns and multiple windows
- Response-time drift becomes meaningful after conflict or vulnerability
- Repair attempts need before-and-after context to be judged
- Affection only matters fully when you can compare it to avoidance and follow-through
How Grey Mirror handles extremely large histories
The product is built to accept very large histories, but it should not hide fidelity behind vague speed language. When a thread is huge, the user experience should say that processing can take longer because Grey Mirror is preserving the countable timeline, participant turns, response gaps, labels, and evidence windows.
Very large uploads should take longer rather than quietly thinning countable metric totals. The report should stay honest about processing time because count fidelity is more important than pretending a giant thread is instant.
That is a better promise than pretending large uploads are instant. The important distinction is this: metric counts, participant splits, response gaps, and taxonomy totals stay grounded in the parsed thread, while model-stage confidence is labeled clearly instead of silently weakening the report.
- Large uploads should show clear processing expectations instead of quiet shortcuts
- Metric counts should stay tied to countable parsed messages, not a hidden sample
- If a model stage needs more evidence, the report should label confidence directly
- Large histories remain useful because sequence, gaps, and aggregate patterns are preserved
Long-history questions this page answers
People looking for a large-context text analyzer often describe the same need in different ways: analyze long message threads, long text conversation analyzer, exported iMessage analyzer, WhatsApp chat analysis, years of texts analysis, or relationship thread analyzer.
Grey Mirror fits that need when the user wants full-thread relationship analysis, not just sentiment on a few lines. This page explains why thread depth matters before sending the reader into the tool.
When to use Grey Mirror versus the quick scan
Use the quick scan when you have a few pasted messages or screenshots and need fast triage. Use Grey Mirror when the question is pattern-heavy: long message thread analysis, repeated ex check-ins, repair decay, one-sided emotional labor, or a relationship that seems to have shifted gradually.
That separation keeps the product honest. The screenshot workflow answers a small-input question; Grey Mirror answers the large-context question.
Frequently Asked Questions
How much context can Grey Mirror really handle?
The current product and parser capacity allows uploads up to 500MB and histories up to 500,000 messages before safety truncation. Very large uploads should take longer rather than quietly thinning countable metric totals.
Does every Grey Mirror model read every line of a huge export directly?
Every countable metric should stay grounded in the parsed message set. On huge exports, the report should show model-stage confidence instead of silently replacing the full thread with a thin sample.
What kinds of searches should land on this page?
People looking for a large-context text analyzer, long message thread analysis, exported chat analysis, or a tool that can read months or years of texts should land here first.