Concerns About New 300 Rows Export Limitation in CSV

William F. · 2025-10-16 14:43:04.690423+00

Can I ask the reasoning behind the new "only 300 rows at a time can be copied" limitation?? I run thousands through and if I'm exporting as csv it screws up the fonts sometimes

Concerns About New 300 Rows Export Limitation in CSV | Clay

12 comments

· Sorted by Oldest

Clay Support
APP
·
·
Hi there, thanks so much for sharing this! We’ll be passing your feedback along to our product team, and any additional context you can provide will help us prioritize with your needs in mind as we shape the roadmap.
Want to chat with someone on the team? Feel free to hit the button below!
Clay Support
APP
·
·
William Finch clicked 'Talk with the team!'
Intercom
APP
·
·
Clay Support is sharing a file with you.
Our support team has got your message and we'll get back to you soon!
If you’re dealing with a specific table, drop the URL below so we can help you quicker. Otherwise, someone from our team will be in touch soon!
Loading attachments
Luca P.
·
·
Hi William, thanks for reaching out to support!
How can I help you today?
William F.
·
·
Hey Luca, I saw you guys added a restriction making it so I cannot copy more than 300 rows at a time, wondering why this was as it is limiting in my workflow
Luca P.
·
·
Yes, we implemented a 300-row limit on copy/paste functionality with our recent table UI updates. For datasets larger than 300 rows, we recommend using the CSV export feature instead. This was an intentional design decision to optimize performance, though we're actively collecting feedback on this change.
William F.
·
·
I find it slows me down drastically, I am now copy-pasting 300 rows at a time as if I use the csv export it can affect the special characters used in peoples names
William F.
·
·
I understand some people were most likely "losing rows" when copying large datasets as the wouldn't scroll and have it all load properly however surely there must be other ways to handle that without limiting everyone?
Nik G.
·
·
Luca P. - New copy/paste limitations are pretty annoying. I don’t even know how to work around it for some things now. Any ideas?
William F.
·
·
actively reducing the functionality of the program is frustrating
💯1
Bo (.
·
·
Hey,
Thanks for sharing this feedback — really appreciate it. We’re passing it along to the product team so they can review the copy/paste limitation and see if there’s room to improve it in future updates.
Let me know if you have any other feedback.
Clay Support
APP
·
·
We haven't heard back from you here, so we're going to go ahead and close this thread out.
Still need help here? Reply back and someone will jump back in.
Have a question thats not related to this thread? We recommend kicking off a new ticket in the support channel!

Clay Support
APP
·
·
Hi there, thanks so much for sharing this! We’ll be passing your feedback along to our product team, and any additional context you can provide will help us prioritize with your needs in mind as we shape the roadmap.
Want to chat with someone on the team? Feel free to hit the button below!
Clay Support
APP
·
·
William Finch clicked 'Talk with the team!'
Intercom
APP
·
·
Clay Support is sharing a file with you.
Our support team has got your message and we'll get back to you soon!
If you’re dealing with a specific table, drop the URL below so we can help you quicker. Otherwise, someone from our team will be in touch soon!
Loading attachments
Luca P.
·
·
Hi William, thanks for reaching out to support!
How can I help you today?
William F.
·
·
Hey Luca, I saw you guys added a restriction making it so I cannot copy more than 300 rows at a time, wondering why this was as it is limiting in my workflow
Luca P.
·
·
Yes, we implemented a 300-row limit on copy/paste functionality with our recent table UI updates. For datasets larger than 300 rows, we recommend using the CSV export feature instead. This was an intentional design decision to optimize performance, though we're actively collecting feedback on this change.
William F.
·
·
I find it slows me down drastically, I am now copy-pasting 300 rows at a time as if I use the csv export it can affect the special characters used in peoples names
William F.
·
·
I understand some people were most likely "losing rows" when copying large datasets as the wouldn't scroll and have it all load properly however surely there must be other ways to handle that without limiting everyone?
Nik G.
·
·
Luca P. - New copy/paste limitations are pretty annoying. I don’t even know how to work around it for some things now. Any ideas?
William F.
·
·
actively reducing the functionality of the program is frustrating
💯1
Bo (.
·
·
Hey,
Thanks for sharing this feedback — really appreciate it. We’re passing it along to the product team so they can review the copy/paste limitation and see if there’s room to improve it in future updates.
Let me know if you have any other feedback.
Clay Support
APP
·
·
We haven't heard back from you here, so we're going to go ahead and close this thread out.
Still need help here? Reply back and someone will jump back in.
Have a question thats not related to this thread? We recommend kicking off a new ticket in the support channel!