CopyMeThat Free Tier Limits - 40-Recipe Cap, Premium Ads, and What Users Should Know

What are CopyMeThat free tier limits in 2026?

The key limit is straightforward:

• Free plan: up to 40 saved recipes
• Paid plan options: around $1 per month, $12 per year, or $65 lifetime
• Model shift: from feature-based premium unlocks to storage-based limits

CopyMeThat also states that features previously marked “premium” are now broadly available. The main gate is no longer feature access. It is recipe count.

That detail matters. It means the lock is applied directly to the core value of the app: your personal recipe library.

Why this hits users so hard

There is nothing inherently wrong with charging for software. Developers deserve to be paid. Sustainable products require revenue.

The frustration comes from how users describe the transition.

Many long-time users report the change appeared without warning. One user described opening the app at 3am with no issues, then finding a paywall at 7am the same morning. Others report messaging that felt transactional: upgrade now, or export and leave.

For people who treated the app like a personal cookbook for years, this is not just about cost. It is about timing, communication, and control over data they already spent years curating.

When users feel surprised instead of prepared, even a low price feels like a penalty.

Premium, but still seeing ads?

This is where the criticism gets sharper.

Some paying users report still seeing ads, including moments where ads interrupt or crowd the interface. If true, this creates a serious perception problem: users are paying subscription fees and still carrying an ad burden.

In most consumer apps, paying is associated with a cleaner experience. That expectation is now standard. So when users report a premium plan with ads still present, they interpret it as double monetization without corresponding quality improvements.

That may not be every user's experience. But it shows up often enough in reviews and complaints that it should not be dismissed as noise.

Reliability complaints are fueling the backlash

Pricing changes are survivable when the product feels stable. They are much harder to accept when users also report reliability decline.

Recent complaints cluster around the same issues:

• Recipe import failures from Instagram, Facebook, and sometimes major publishers
• Slower search and deletion workflows
• App instability after updates, including crashes and repeated reopen attempts
• Print and popup workflow friction
• Support emails that users say go unanswered

Even one of these issues can reduce trust. Together, they create a narrative that the product is asking for more money while delivering less confidence.

That narrative is dangerous for any subscription app, because subscriptions depend on ongoing trust, not one-time excitement.

Context: a founder-led product under strain

To be fair, CopyMeThat appears to be a founder-led product under Tine Bak LLC. Tine Bak has been the public face of the company since founding it in 2012, and the operational footprint suggests a small team supported by specialized contractors for mobile app maintenance and server infrastructure.

That context helps explain some of the strain. Running a mature consumer app with mobile maintenance, backend reliability, import compatibility, customer support, and pricing transitions is hard even for larger teams.

But users do not experience "team size." They experience product behavior.

When policy changes, reliability issues, and support gaps happen at the same time, users do not read it as operational constraints. They read it as declining product stewardship.

You can acknowledge the challenge and still say the rollout was mishandled.

What to do if you are near or over the 40-recipe limit

If you rely on CopyMeThat heavily, treat this as a practical risk-management moment, not just a pricing debate.

1. Export your data now. Do this before making any account or subscription decisions.
2. Document your workflows. If you rely on import flows, tags, meal plans, or shopping lists, list what must survive a migration.
3. Check ad behavior on your current plan. If you are paying and still seeing intrusive ads, capture screenshots and dates for support requests.
4. Set a support response threshold. If support does not respond in a reasonable window, assume migration may be necessary.
5. Evaluate alternatives by principles, not branding. Prioritize no hard recipe cap, transparent pricing, strong export and import, and clear support expectations.

The goal is simple: your recipe library should belong to you, not to a plan change.

Frequently asked questions