The CAASPP secure browser is a specialized application required for students to take California's Smarter Balanced Assessments and other state-mandated tests online. Unlike a standard web browser, the CAASPP secure browser locks down the testing environment by disabling access to external websites, applications, and system tools during the exam session. This ensures test integrity and prevents students from accessing unauthorized resources while answering questions. For anyone navigating caaspp technical requirements, understanding how the secure browser works is essential preparation before test day arrives.

California's statewide assessment program covers grades three through eight and grade eleven, testing students in English Language Arts and Mathematics. All online testing components must be administered using the approved secure browser. Schools and districts are responsible for installing and maintaining the secure browser on every device that will be used for testing, which means IT staff, teachers, and technology coordinators all need to be familiar with its setup and operation. Students who arrive at a testing station where the secure browser is not properly configured may face delays or be unable to test at all.

The secure browser is developed and maintained by the California Department of Education (CDE) in partnership with the Smarter Balanced Assessment Consortium and the testing vendor. It is updated each year before the testing window opens, which means older versions installed from previous years will not work. Schools must download and install the current version annually, and in many cases, updates must be pushed to every device across an entire campus network before the first student can log in to the assessment platform.

One of the most commonly misunderstood aspects of the CAASPP secure browser is that it is not a single universal application. There are separate versions for different operating systems including Windows, macOS, ChromeOS, iPadOS, and Linux. Each operating system version has its own installation process, its own set of minimum hardware requirements, and its own configuration steps. Using the wrong version or an outdated package is a frequent source of test-day technical failures, so verifying the correct download before testing begins is a critical step for any school technology team.

The secure browser also plays a role in administering accommodations and accessibility features for students with disabilities. Text-to-speech, zoom tools, color contrast settings, and other built-in accessibility options are all delivered through the secure browser interface. These features are configured in the student's test settings before the assessment window opens, but the secure browser must be installed and functioning correctly for those settings to activate properly during testing. Any device incompatibility that prevents the browser from launching will also block access to these important accommodations.

Parents and students often wonder whether there is anything they need to do personally to prepare the secure browser at home. In most cases, the CAASPP tests are administered at school on district-managed devices, so families do not need to install the secure browser themselves. However, with the rise of bring-your-own-device policies and, in some limited circumstances, remote testing arrangements, it is worth understanding how the browser works and why it behaves differently from Chrome or Safari. Knowing what to expect can reduce confusion and anxiety on the day of the assessment.

This guide covers everything you need to know about the CAASPP secure browser: what it does, how it is installed, the technical requirements it demands, how to troubleshoot common problems, and what both students and educators should keep in mind when preparing for California's statewide assessments.

Whether you are an IT coordinator managing a fleet of school Chromebooks, a teacher preparing your class for testing week, or a student curious about how the online exam works, the information here will give you a thorough, practical understanding of one of the most critical pieces of technology in California's public school assessment infrastructure.

Installing the CAASPP secure browser is a multi-step process that begins well before the official testing window opens. The California Department of Education publishes updated installation packages on the California Assessment of Student Performance and Progress portal, typically releasing new versions in late fall or early winter to give schools adequate time for deployment. Technology coordinators should bookmark the official download page and set calendar reminders to check for new releases each year rather than assuming a previous installation remains current and compatible.

For Windows and macOS devices, the installation process involves downloading an executable or package file from the CDE portal and running it with administrator privileges. On managed networks, many districts use software deployment tools such as JAMF, Microsoft Endpoint Configuration Manager, or similar platforms to push the installer to hundreds or thousands of devices simultaneously. This approach is far more efficient than manually visiting each machine, and it also allows IT staff to verify successful installation across the entire device fleet from a central dashboard before testing begins.

ChromeOS deployment follows a different path because the secure browser extension is managed through the Google Admin Console rather than a traditional software installer. The district's Google Workspace administrator must navigate to the Chrome Management section, locate the CAASPP Secure Browser app in the Chrome Web Store or enter the application ID manually, and then force-install it on the relevant organizational units containing student devices. Once deployed, the extension appears automatically on student Chromebooks without any action required on the student's part, which simplifies the experience considerably on test day.

iPad deployment through Apple School Manager requires the testing app to be purchased or acquired at no cost through Apple's Volume Purchase Program and then assigned to specific devices or device groups. Schools using Mobile Device Management platforms like Jamf School or Mosyle can push the app silently to enrolled iPads. Guided Access or Autonomous Single App Mode must also be configured in the MDM profile so that when the test launches, the iPad automatically locks to the testing application and students cannot exit to the home screen or switch to another app mid-assessment.

After installation, administrators should run a technology readiness check using the tools provided in the California Assessment Portal. These readiness checks verify that the secure browser is installed, that it can connect to the testing servers, and that the device meets all minimum hardware and software requirements. Running these checks at least two weeks before the testing window opens gives schools enough time to address any failed devices, reimage machines with problems, or procure replacement hardware if necessary. Waiting until the week before testing to run readiness checks is a common and costly mistake.

Student login credentials for the CAASPP are managed through the California Longitudinal Pupil Achievement Data System, commonly known as CALPADS. Each student has a unique Statewide Student Identifier that serves as their username for the testing platform. Test administrators receive session ID codes that students use to join an active test session, and these codes change for each testing session. Understanding this login flow is important because students who launch the secure browser for the first time on test day and encounter an unfamiliar login screen may become confused if they have not been walked through the process beforehand.

Training students to launch the secure browser is a step that many teachers underestimate. Walking students through a practice session using the state-provided practice tests allows them to experience the full secure browser environment without any stakes attached. They can get comfortable with the interface, see how the locked-down environment behaves differently from their normal browser experience, and practice using any accessibility tools they will rely on during the actual assessment. This preparation time is genuinely valuable and reduces test-day anxiety for both students and proctors.

Troubleshooting the CAASPP secure browser is a skill every school technology coordinator and test administrator needs to develop before the testing window opens. The most frequent issue that surfaces on test day is the browser refusing to launch because of a conflicting application running in the background. When this happens, the browser displays an error message that identifies the conflicting software by name.

The fix is straightforward: close or disable the named application and attempt to relaunch the browser. However, some applications like remote desktop agents or system monitoring tools may restart automatically after being closed, requiring the application to be fully disabled in system services rather than just terminated.

A second common issue involves network connectivity failures that occur after the student has already launched the browser and started a test. These failures typically present as a spinning loading indicator or a sudden error screen mid-question. In most cases, the student's progress is automatically saved on the server up to the point where the connection dropped, so no completed work is lost.

The proctor should pause the student's test through the Test Administrator Interface, have the student close the secure browser, verify the network connection, and then relaunch the browser to resume the session. Proctors should resist the urge to restart the test from the beginning, as this would erase the student's saved responses.

Version mismatch errors are another troubleshooting scenario that technology staff encounter regularly. If a device has an outdated version of the secure browser installed from a previous testing year, the application may launch successfully but then fail to connect to the testing servers because the server-side infrastructure no longer supports the older client.

The browser will typically display a message indicating that the version is not supported or that an update is required. The fix is to uninstall the old version and install the current version from the CDE portal, a process that usually takes only a few minutes on a single device.

For Chromebook users, the most common troubleshooting scenario involves the managed extension not appearing on the student's device even though it appears to be deployed in Google Admin Console. This is usually a sync delay issue: Chrome devices check in with the Admin Console periodically, and newly deployed extensions may not appear immediately after deployment. Forcing a policy refresh by navigating to chrome://policy in the device's browser, or simply signing out and back in to the managed Chromebook, typically resolves the sync delay and causes the extension to appear within minutes.

iPad-specific issues often center on Guided Access configuration. If Guided Access is not properly set up, students can exit the testing application by pressing the home button or swiping up, which automatically ends their test session and may create a security flag in the Test Operations Management System. Technology coordinators should test the Guided Access configuration on a sample device before deploying it to the entire iPad fleet, confirming that the device locks to the testing application correctly and that the triple-click shortcut used to exit Guided Access (known only to the test administrator) works as expected.

The CDE's Help Desk is available during the testing window to assist with issues that cannot be resolved using the standard troubleshooting guidance. Schools can reach the Help Desk by phone or through a ticketing system accessible from the California Assessment Portal. When calling, technology coordinators should have the affected device's operating system version, the secure browser version number, and any error codes or messages readily available.

Having this information prepared significantly reduces the time spent on the call and increases the likelihood of a quick resolution. The Help Desk also maintains a known issues log that documents widespread problems affecting multiple schools, which is worth checking before calling to see if a solution has already been published.

After each testing window closes, technology coordinators should document any devices that experienced repeated failures, any network settings that required adjustment, and any error codes that proved particularly difficult to resolve. Building a troubleshooting log specific to your school or district creates an institutional knowledge base that makes each subsequent testing cycle smoother and faster to prepare for. Many of the same technical issues recur from year to year, and having documented solutions means that new staff can quickly get up to speed without having to rediscover solutions that experienced staff already know.

Accessibility and accommodation settings within the CAASPP secure browser represent one of the most important aspects of the testing platform for students with disabilities and English learners. The Smarter Balanced Assessment platform offers two categories of supports: universal tools available to all students, and designated supports and accommodations available to students who qualify based on an Individualized Education Program, a 504 Plan, or an English learner designation.

All of these features are delivered through the secure browser, and they must be configured in the student's test settings before the test session begins — they cannot be added or changed once the student has launched their test.

Universal tools that all students can access through the secure browser include the digital notepad, a highlighter, a line reader, zoom in and out functions, a global notes feature, and a strikethrough tool for eliminating answer choices. These tools appear as icons in the test interface and are available without any prior configuration.

Students benefit from becoming familiar with these tools during practice test sessions, as the time it takes to discover and figure out how to use them during an actual assessment is time not spent answering questions. Teachers can walk students through each tool during classroom instruction using the publicly available practice tests.

Designated supports are pre-configured features that require documentation of a student's specific needs but do not require a formal IEP or 504 Plan. These include color contrast settings, text-to-speech for Mathematics (ELA text-to-speech requires an IEP or 504), translated test directions for English learners, bilingual glossaries, and Spanish versions of the Mathematics assessments.

Test coordinators enable these supports in the TOMS for each qualifying student before the testing window opens. If a student arrives on test day and their designated supports are not showing in the secure browser, the issue is almost always that the support was not enabled in TOMS — not a browser malfunction.

Formal accommodations for students with IEPs or 504 Plans include items such as text-to-speech for ELA reading passages, extended testing time, separate testing environments, print-on-demand for test questions, and human reader or human signer delivery. These accommodations must be documented in the student's plan and enabled in TOMS by the test coordinator.

Some accommodations, such as human reader delivery, involve a test examiner reading test content aloud to the student while the student still interacts with the secure browser on a device. In these cases, the device must still have the secure browser installed and running, and the test examiner must be trained in accommodation delivery procedures.

Text-to-speech is delivered directly through the secure browser's built-in audio engine. When this accommodation is enabled, a speaker icon appears next to eligible text elements, and the student can click the icon to have the content read aloud. The quality and naturalness of the text-to-speech voice has improved significantly over recent testing cycles, and most students adapt to it quickly.

However, schools should ensure that devices used by students with text-to-speech accommodations have functioning speakers or that students are provided with headphones, as the audio is essential to this accommodation's effectiveness and a faulty audio output would constitute a significant barrier to access.

For students who use assistive technology devices such as screen readers, refreshable Braille displays, or alternative input devices, compatibility with the CAASPP secure browser requires careful verification. The CDE publishes a list of approved assistive technologies tested for compatibility with the current secure browser version.

Technology coordinators should cross-reference a student's assistive technology setup against this compatibility list each year, as compatibility can change when either the secure browser or the assistive technology software receives an update. When incompatibilities are identified, the school should contact the CDE Help Desk to discuss alternative testing arrangements well in advance of the testing window.

Ensuring that all accommodation and accessibility configurations are in place before test day is ultimately a shared responsibility among the test coordinator, the classroom teacher, the special education case manager, and the technology coordinator.

A systematic review process — checking every enrolled student's TOMS settings against their current IEP or 504 Plan accommodations at least one week before testing — is the most reliable way to ensure no student arrives at a testing session missing supports they are legally entitled to receive. This kind of proactive coordination is what separates smooth testing administrations from ones filled with last-minute calls to the Help Desk.

Preparing students for the CAASPP secure browser experience is just as important as the technical setup work done by IT staff. When students encounter a completely locked-down interface for the first time during a high-stakes assessment, the unfamiliarity itself can create test anxiety that affects performance.

The simplest and most effective way to address this is to give every student at least one full practice session using the secure browser and the state-provided practice tests before the official assessment window opens. California's portal offers publicly accessible practice tests for every grade level and subject area that replicate the full testing experience, including the secure browser environment.

Teachers preparing students for the CAASPP should make sure students understand a few key realities of the secure browser environment. First, they cannot open a second tab or window to look something up — the browser blocks this completely. Second, the interface may look and feel different from the Google Chrome or Safari browser they use every day for schoolwork.

Third, if the screen goes black or the browser closes unexpectedly, they should raise their hand immediately rather than trying to restart on their own, because the proctor needs to resume the session through the Test Administrator Interface to prevent data loss or session errors.

Students should also be aware of how the testing interface handles different question types. The CAASPP includes multiple choice questions, but it also features constructed response items where students type extended answers, technology-enhanced items where students drag and drop, fill in tables, or match items by clicking and connecting, and performance tasks that require multi-step written responses. All of these interaction types are handled within the secure browser, and students who have never practiced with them may struggle to understand the mechanics of how to submit their answers even if they know the underlying content well.

For mathematics testing, students should know which tools are built into the secure browser and which physical tools may be permitted. A digital calculator is provided within the browser for calculator-allowed sections, and it automatically appears only on the appropriate questions. Scratch paper may be distributed by the proctor for mathematics testing. Students should not attempt to use external calculator applications or devices, as the secure browser will block access to any application outside of the testing interface and proctors are required to document and report the use of unauthorized tools.

Time management is a skill that students can practice using the secure browser's built-in countdown timer, which is visible throughout the test session. The timer helps students pace themselves across sections, but some students find it anxiety-inducing. Teachers can walk students through strategies for working with the timer rather than against it: checking it only at defined intervals, flagging difficult questions to return to rather than spending too long on a single item, and using the review screen to confirm that all questions have been answered before submitting the section.

Students who experience technical problems during the actual assessment — not during practice — should know exactly what to do: stop what they are doing, raise their hand, and wait for the proctor. They should not attempt to close and reopen the browser on their own, because doing so outside of the proctor-managed resume process can create session errors. Training students in this simple protocol before test day removes a major source of confusion and ensures that proctors can manage technical incidents quickly without disrupting the entire testing room.

Finally, remind students that their responses are saved continuously as they work through the test. They do not need to manually save their answers, and a brief network hiccup will not erase their completed work as long as the proctor resumes the session properly if the connection drops. Understanding that the system is designed to protect their work can relieve a significant source of stress, especially for students who have experienced data loss in other digital environments and approach online testing with heightened worry about losing their responses before submission.