SQLite Forum

Setting non-binary columns to null in a table with a binary column populated with data creates free space and a larger file
> the file size continues to grow when the update command is executed

It doesn't grow with every UPDATE statement, only the first, correct?

i.e. if you execute one of your UPDATE statements you should end up with X or fewer free pages in db, where X is the number of overflow pages the largest record in the table uses. Executing subsequent updates of the type you mention should not change this - there will still only be X or fewer free pages in the db.