Soda PDF edits the elements that already exist on a PDF page and can add new ones. A page can contain editable text boxes and images. Soda PDF can also place shapes or form fields on that page. It has a separate control for signatures. The editor treats each element separately, so text that looks like one paragraph may belong to several boxes. This object-based approach explains why editing a PDF differs from typing into a continuous word-processing document.
Visible words are not always editable text
In Edit Mode, Soda PDF draws a blue border around an editable text box. Clicking inside the border places the cursor in the text that belongs to that box. The user can then change the text or adjust its box. A paragraph can arrive as several separate boxes even when it looks continuous on the page. The context command “Merge Text Blocks” joins selected text parts when that separation makes an edit awkward.
A scanned page behaves differently. Soda PDF identifies the page as an image and draws a red border around it. The visible letters remain part of the image at that stage. OCR must read the page before Soda PDF can expose those letters as editable text. The border color therefore answers a practical question before an edit begins: blue identifies a text box, while red identifies an image that needs OCR.
Formatting can change without changing the characters
Soda PDF separates text formatting from annotations. Font and size change the selected text. Spacing and alignment also belong to the text box, along with indentation. Underline is an annotation placed over the text. Highlight and strikethrough work as annotations too. These commands therefore create removable marks without rewriting the characters below them.
Fonts create another practical limit. A PDF can contain an embedded font that the computer does not have. Soda PDF substitutes an installed font that resembles the missing one, and newly entered text can look different from the surrounding material. Installing the missing font and restarting Soda PDF makes that typeface available to the editor. Until then, the substitute remains visible in the changed text.
The browser editor works through an uploaded copy
The online editor begins with an upload from local storage. It can also open a file from Google Drive or Dropbox. The editor then exposes controls for text and images. Other controls add shapes or form fields, and a separate control handles signatures. After the edit, Soda PDF can download or print the result. It can also email the file or save it to supported cloud storage.
This workflow creates a clear boundary between editing and obtaining the result. The page can accept changes before the current access policy permits every output action. Some online editing actions remain usable until Soda PDF asks for an upgrade at the download, print, email, or save step. The restriction can therefore appear after the document already contains edits.
Compression trades image detail for a smaller copy
The Compress command sits under Create & Convert. Soda PDF asks for a compression level and displays an estimated output size before it runs. Compression reduces the quality of graphical content to reduce the file size. The command writes a separate compressed copy, so the compression result and the source remain distinct files.
The free quick tools apply two further limits. They restrict how many files a user can process, and they restrict the accepted input size. These limits belong to the quick-tool access policy.
