Scrivener Problems & Issues

Real user-reported problems, complaints, and limitations for Scrivener. Based on analysis of 9 signals.

Issues by Category

usability5 issues

Notoriously steep learning curve takes weeks to master

Users consistently report that Scrivener's learning curve is extremely steep - described as 'not a curve, it's a cliff.' Many users spend months before feeling comfortable with basic workflows. The software has so many features that at first, it feels more like a machine from the future than a simple text editor. Users report giving up in frustration after initial attempts.

Frequency: 9%Sentiment: -0.75/10085 sources
Impact
9

Compile feature is confusing nightmare for many users

The 'Compile' feature for exporting manuscripts is widely criticized as incredibly confusing. Users describe it as a 'minor nightmare' with incomprehensible settings. Scrivener 3's compile is considered more difficult than version 2. Many users have no idea how to use Compile even after months of use. Forum threads are full of frustrated users trying to understand the compile process.

Frequency: 8%Sentiment: -0.80/10060 sources
Impact
8

Interface is unintuitive patchwork design

The interface feels like a patchwork of basic functionality with miscellaneous add-ons. There's no consistent UI between various components. Some screens are ridiculously small, unusable, or mysterious. The software is not intuitive by any stretch - users spend significant time just learning where features are located.

Frequency: 6%Sentiment: -0.55/10035 sources
Impact
6

No cloud or web version - desktop only with sync workarounds

Scrivener is local-only with no cloud version or web app. Users cannot access their work from another computer without manual setup. Syncing between devices requires Dropbox or iCloud configuration, which some users find unreliable. Occasional syncing inconsistencies are reported with multi-device setups.

Frequency: 5%Sentiment: -0.55/10028 sources
Impact
6

Image insertion causes massive file size bloat

Inserting images directly into drafts leads to massive file sizes on compile. There's no easy way to resize images in ways that commensurately reduce the image file size. Users working on illustrated manuscripts or research documents with images face significant export problems and unwieldy file sizes.

Frequency: 4%Sentiment: -0.50/10015 sources
Impact
5
reliability3 issues

Windows version has significant bugs and quality issues

The Windows version lags behind Mac in features and stability. Users report bugs in text formatting, copy/paste operations, and general unreliability. The Windows version historically received updates later and with less polish than Mac. Some features work differently or are missing compared to Mac.

Frequency: 7%Sentiment: -0.65/10045 sources
Impact
7

Table handling is completely broken

Software marketed for writers can't properly handle tables - a basic feature. Copy-pasting tables from websites, Word, or Excel results in broken formatting. Bullet points don't align correctly with title text. Users who need tables for research notes or data find this extremely frustrating.

Frequency: 6%Sentiment: -0.70/10025 sources
Impact
6

Slow development pace with years between major updates

Users complain that Scrivener has barely improved through years of development. Literature & Latte is a tiny team, resulting in long gaps between significant updates. They charge for new major versions, frustrating users who feel the updates don't justify additional payment. Feature requests take years to implement, if ever.

Frequency: 5%Sentiment: -0.60/10030 sources
Impact
5
mobile1 issue

No Android version - iOS mobile only

Scrivener only offers iOS for mobile, completely excluding Android users. The iOS app costs an additional $23.99. Users on Android have no native mobile option and must rely on syncing workarounds. This locks out a significant portion of potential users who use Android devices.

Frequency: 6%Sentiment: -0.65/10040 sources
Impact
7

Regret Patterns

Common reasons users regret choosing Scrivener.

Spent weeks learning only to realize they don't need it

Users invest significant time mastering Scrivener's complex features only to realize their writing needs are simpler. They could have used Google Docs or Word all along but feel locked into Scrivener after the learning investment.

Frequency: 7%After 1-3 months

Can't figure out compile and give up on export

Users complete their manuscript but get stuck trying to export/compile it properly. The compile feature's complexity becomes a roadblock at the finish line, causing some to manually copy-paste into Word for formatting.

Frequency: 8%When finishing a project

Bought iOS app only to struggle with sync

Users purchase the separate $24 iOS app expecting seamless mobile writing but encounter syncing issues with Dropbox/iCloud. Projects don't sync reliably, causing lost work or duplicate files.

Frequency: 5%Within first month of mobile use

When Scrivener Breaks Down

Specific scenarios where Scrivener fails or underperforms.

Need to collaborate with editor or co-author

Scrivener's single-user, local-only design falls apart when collaboration is needed. Users must export to Word/Google Docs to share, losing Scrivener's organizational benefits. Track changes happen outside Scrivener.

Working across multiple devices or on the go

Without native cloud sync, working across devices requires careful Dropbox/iCloud setup. Sync conflicts can corrupt projects. Users switching between Mac, Windows, and iOS face the most issues.

Deadline pressure with no time to learn features

Writers on tight deadlines can't afford weeks to learn Scrivener. The steep learning curve makes it unsuitable for urgent projects. Users end up fighting the software instead of writing.