Question

How large of a file (tokenized / detokenized data records) can I upload to Turing Ul; if I have the necessary access?
1,000,000
500,000
100,000
50,000

Answer 1

I don’t have enough detail to give a definitive number — “Turing UI” could refer to different products with different quotas. Could you tell me which service/portal you mean (vendor and URL or product name) and whether you’re on a particular plan or have admin/enterprise access?

Meanwhile, practical guidance that should help regardless of exact platform:
- Many web UIs impose per-file or per-upload limits (common breakpoints are 50k, 100k, 500k records) or file-size limits (e.g., hundreds of MBs to a few GB). Enterprise/whitelisted accounts sometimes allow much larger uploads.
- If your dataset is tokenized, it will usually be larger (in bytes) than the same data detokenized; check token count → byte size to estimate actual file size.
- If the UI limits are too small, typical solutions are:
- Split the dataset into multiple files (e.g., 50k–100k records per file) and upload parts.
- Host the full dataset in object storage (S3, Azure Blob, GCS) and give the service a pointer/URI for server-side ingestion.
- Use an API or CLI that supports chunked uploads or streaming ingestion rather than the browser UI.
- If you can, check the product documentation or your account admin for “file upload limits,” “dataset size limits,” or “ingestion quotas.” Support/CS can often raise limits for enterprise customers.

If you tell me the exact Turing UI product and your access level (standard vs enterprise), I can look up or estimate the specific allowed maximum and suggest an upload strategy (split sizes, chunking, or storage workaround).