Self-contained, embeddable, zero-configuration SQL database engine

SQLite for Mac

SQLite 3.35.3

  -  1.4 MB  -  Freeware

Sometimes latest versions of the software can cause issues when installed on older devices or devices running an older version of the operating system.

Software makers usually fix these issues but it can take them some time. What you can do in the meantime is to download and install an older version of SQLite 3.35.3.


For those interested in downloading the most recent release of SQLite for Mac or reading our review, simply click here.


All old versions distributed on our website are completely virus-free and available for download at no cost.


We would love to hear from you

If you have any questions or ideas that you want to share with us - head over to our Contact page and let us know. We value your feedback!

  • SQLite 3.35.3 Screenshots

    The images below have been resized. Click on them to view the screenshots in full size.

    SQLite 3.35.3 Screenshot 1

What's new in this version:

- Enhance the OP_OpenDup opcode of the bytecode engine so that it works even if the cursor being duplicated itself came from OP_OpenDup. Fix for ticket bb8a9fd4a9b7fce5. This problem only came to light due to the recent MATERIALIZED hint enhancement.
- When materializing correlated common table expressions, do so separately for each use case, as that is required for correctness. This fixes a problem that was introduced by the MATERIALIZED hint enhancement.
- Fix a problem in the filename normalizer of the unix VFS
- Fix the "box" output mode in the CLI so that it works with statements that returns one or more rows of zero columns (such as PRAGMA incremental_vacuum)
- Improvements to error messages generated by faulty common table expressions
- Fix some incorrect assert() statements.
- Fix to the SELECT statement syntax diagram so that the FROM clause syntax is shown correctly
- Fix the EBCDIC character classifier so that it understands newlines as whitespaced
- Improvements the xBestIndex method in the implementation of the (unsupported) wholenumber virtual table extension so that it does a better job of convincing the query planner to avoid trying to materialize a table with an infinite number of rows.