Don't even try to modify the table: that's the wrong approach.
I assume you are trying to add columns because you have an unknown number of images related to a specific row, and think that adding a column for each will do what you want. It won't. When you add a column, you add it to every row in the table - so if you have one row which needs space for 20 images then every row gets that space, even if they have only one image.
Instead, don't have any rows in the table for storing images at all!
Lets assume these are product pictures, and that a product can have a variable number of images - just as something for sale on eBay or Amazon might.
You have your Products table:
ID INT, IDENTITY (or UNIQUEIDENTIFIER, depending on your preference)
Title NVARCHAR(255)
Description NVARCHAR(MAX)
Price DECIMAL(8,2)
Stock INT
But instead of adding IMAGE columns, you create a second table Images:
ID INT, IDENTITY (Or UNIQUEIDENTIFIER)
ProductID Same as ID in the Products table, FOREIGN KEY to Products.ID
ImageData IMAGE
You can then add as many images as you need to a Product, and retrieve them using the Product ID when you need them.