Client-side processing is work performed on a user’s device, such as in a web browser, rather than on a remote server. A browser-based design tool might use it to display or modify a model locally, while a desktop application generally performs much of its work on the computer where it is installed.
Keeping work on the device can improve responsiveness and reduce how much data must be sent to a server. It also introduces security considerations: code running in the browser may handle sensitive files or inputs, and locally processed data can still be exposed to malicious scripts, unsafe extensions, or compromised devices. Defenses include validating untrusted files and automation inputs, isolating components, and limiting access to local resources. Client-side processing describes where work happens; it does not by itself guarantee that the work or data is secure.