UnTXT lives at untxt.uk as part of the CVaaS ecosystem, and because it runs in a browser there is nothing at all to install. Signing in goes through Google OAuth. The first 1,000 words are analysed free when you sign up, which is enough to form a fair opinion of it.
UnTXT solves one specific problem. When somebody reads a piece of writing and suspects that parts of it were machine written, what they need to know is which parts, and why. A percentage will never tell you which sentence to rewrite. Actually that is the whole complaint with percentage scores, and it is the one thing this does answer.
| User | Use case |
|---|---|
| Student | Checking an essay or dissertation for AI-generated passages before submission |
| Teacher | Reviewing student submissions and downloading a PDF analysis report |
| Professional | Scanning business documents, reports, or applications for AI authorship |
UnTXT is a trademark of Sataklela OÜ, registration pending, and Sataklela OÜ is who builds and runs it. It belongs to the CVaaS family of tools, which all live under untxt.uk.
Go to untxt.uk and sign in. Authentication runs through Google OAuth, so there is no separate account to create first. Your first 1,000 words are free, and nobody asks you for a card before you start.
Loughborough University students: the generative AI policy for assessments and UnTXT sit together without friction, because this detects rather than generates. Audit a draft with it, and you have evidence of good scholarship rather than a problem to explain. Best practice, honestly, is to acknowledge that use in your assessment statement.
Students at UCL: the university takes a supportive rather than prohibitive line on AI, and auditing your own draft fits that comfortably. UCL asks that a final submission be "substantially your own work", which is exactly the thing a check like this lets you verify before anyone else reads it. Acknowledge the use in your assessment disclosure.
Imperial College London: the requirement there is that "using AI to create assessed work" needs explicit authorisation. Auditing a draft supports that rather than working around it, since you find the machine written passages and rewrite them, and your substantial personal contribution stays intact. Acknowledge the use in your AI tools statement.
Anywhere in the Russell Group: the shared principles emphasise transparency alongside substantial personal contribution, and both are served by checking your own work. Even so, read your own institution's AI policy, because the detail really does vary from one to the next.
Educators, at any institution: reviewing submissions for AI patterns is exactly what this was built to do, and it holds up well enough for assessment integrity work.
Everywhere else: whether UnTXT is compliant depends on the AI policy your own institution has written. Broadly it supports transparent scholarly practice, because it lets a student audit a draft before submitting it.
Start for free - no payment required