---
updatedAt: 2026-06-01T07:55:16.000Z
agentTools:
  siteIndex: https://docs.jfrog.com/llms.txt
  projectIndex: https://docs.jfrog.com/artifactory/llms.txt
---

# Platform Search

The platform search box at the top of the JFrog Platform UI supports the following search methods:

* [Search by keywords](#search-by-keywords)
* [Free-text search](#free-text-search)
* [Advanced search using filters](#advanced-search-using-filters)

The platform search box is always available from any window, and the selected Search view changes depending on where you are in the Platform. For example, the Packages search is active when you are in the Packages page.

<Image align="center" border={true} width="40% " src="https://files.readme.io/900d9de8dbb4cfb77a48736b155c4fec63f69084f2d8b50f067f3b169d12441e-platform-UI_search-window.png" className="border" />

<Callout icon="📘" theme="info">
  **Product-Specific Requirements**

  The following search types require the following to be installed with their associated licenses:

  * Release Bundles Search: For Release Bundles v1, requires JFrog Distribution to be installed with an Enterprise+ license. For Release Bundles v2, requires Pro or above.
  * Security & Compliance Search: Requires JFrog Xray to be installed with a Pro X, Enterprise with Xray, or an Enterprise+ license.
</Callout>

**To search for an object**:

1. From any page in the platform UI, click the dropdown button next to the search field and choose the type of item you want to search for.
2. Enter a search term and click **Enter**. The search results appear.
3. Click the item you want to view. That item loads in the window and its properties are displayed.

<Callout icon="🐸" theme="default">
  Learn more about **[Search Best Practices](https://academy.jfrog.com/jfrog-artifactory-search-best-practices)** at JFrog Academy!
</Callout>

## Search Syntax

The platform search supports the following syntax:

* Keyword-based search.
* Case-sensitive search.
* Wildcard characters `*` and `?`

For example, when searching for a package named `angular`, typing `an*`, `angula?` returns `angular`.

## Search by Keywords

You can use predefined keywords in the platform search to effectively and specifically narrow your search.

The Advanced search filter is also based on these keywords. Selecting a filter in the Advanced search populates the associated keyword in the search bar. For more information, see [Advanced Search Using Filters](#advanced-search-using-filters).

<Image align="center" src="https://files.readme.io/343770273cbf4fe361b654dfd532e9950885d800ac46f4e368b4f07df9f05e81-search-by-keyword.png" />

### General Keywords

The following table lists keywords that you can use in any platform search.

<Table align={["left","left"]}>
  <thead>
    <tr>
      <th>
        Keyword
      </th>

      <th>
        Description
      </th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>
        `pkg`
      </td>

      <td>
        Searches by package type.

        For example: `pkg:docker`returns results for Docker packages.
      </td>
    </tr>

    <tr>
      <td>
        `repo`
      </td>

      <td>
        Searches by repository type: local, remote, virtual, or distribution.

        For example: `repo:docker-local type:package myApp` returns results for packages in the docker-local.
      </td>
    </tr>

    <tr>
      <td>
        `checksum`
      </td>

      <td>
        Searches by the checksum of the package or artifact.

        For example: `checksum:13f2ab8fa` returns results for packages or artifacts containing the checksum number`.`
      </td>
    </tr>

    <tr>
      <td>
        `properties`
      </td>

      <td>
        Searches for artifacts that are annotated with properties.

        For example: `properties: passedQA=true,oss=true`returns results for packages that have passed QA and are OSS.
      </td>
    </tr>

    <tr>
      <td>
        `before`
      </td>

      <td>
        Searches for resources that were created before the specified date.

        For example: `pkg:docker before:2019-01-03` returns results for Docker packages created before this date.
      </td>
    </tr>

    <tr>
      <td>
        `after`
      </td>

      <td>
        Searches for resources that were created after the specified date.

        For example: `pkg:docker after:2019-01-03` returns results for Docker packages created after this date.
      </td>
    </tr>

    <tr>
      <td>
        `cve`
      </td>

      <td>
        Searches for resources that have the specified issue.

        For example: `cve:CVE-2019-12` returns results for resources affected by `CVE-2019-12.`
      </td>
    </tr>

    <tr>
      <td>
        `license`
      </td>

      <td>
        Searches for resources containing the specified license.

        For example: `license:MIT` returns results for resources containing the MIT license.
      </td>
    </tr>

    <tr>
      <td>
        `severity`
      </td>

      <td>
        Searches for resources contain a violation with a specific severity level.

        For example: `severity:medium,high` returns results for resources containing security violations with Medium and High severity levels.
      </td>
    </tr>
  </tbody>
</Table>

### Artifact Keywords

The following table lists keywords for Artifacts searches.

<Table align={["left","left","left"]}>
  <thead>
    <tr>
      <th>
        Keyword by Search Type
      </th>

      <th>
        Supported Package Type
      </th>

      <th>
        Supported Values
      </th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>
        **Artifacts**
      </td>

      <td>

      </td>

      <td>

      </td>
    </tr>

    <tr>
      <td>
        `searchType`
      </td>

      <td>

      </td>

      <td>
        `Packages`, `Archive`, `Properties`, `Checksum`, or `Trash.`
      </td>
    </tr>

    <tr>
      <td>
        **Artifacts > Packages**
      </td>

      <td>

      </td>

      <td>

      </td>
    </tr>

    <tr>
      <td>
        `version`
      </td>

      <td>
        All Packages
      </td>

      <td>
        Searches for artifacts according to a specific version.
      </td>
    </tr>

    <tr>
      <td>
        `category`
      </td>

      <td>
        Chef
      </td>

      <td>
        Free text
      </td>
    </tr>

    <tr>
      <td>
        `platform`
      </td>

      <td>
        Chef and Conda
      </td>

      <td>
        Free text
      </td>
    </tr>

    <tr>
      <td>
        `user`
      </td>

      <td>
        Conan
      </td>

      <td>
        Free text
      </td>
    </tr>

    <tr>
      <td>
        `channel`
      </td>

      <td>
        Conan
      </td>

      <td>
        Free text
      </td>
    </tr>

    <tr>
      <td>
        `os`
      </td>

      <td>
        Conan
      </td>

      <td>
        Free text
      </td>
    </tr>

    <tr>
      <td>
        `arch`
      </td>

      <td>
        Conan, Conda, Debian, Opkg, RPM
      </td>

      <td>
        Free text
      </td>
    </tr>

    <tr>
      <td>
        `buildType`
      </td>

      <td>
        Conan
      </td>

      <td>
        Free text
      </td>
    </tr>

    <tr>
      <td>
        `compiler`
      </td>

      <td>
        Conan
      </td>

      <td>
        Free text
      </td>
    </tr>

    <tr>
      <td>
        `priority`
      </td>

      <td>
        Debian, Opkg
      </td>

      <td>
        Free text
      </td>
    </tr>

    <tr>
      <td>
        `maintainer`
      </td>

      <td>
        Debian, Opkg
      </td>

      <td>
        Free text
      </td>
    </tr>

    <tr>
      <td>
        `dist`
      </td>

      <td>
        Debian
      </td>

      <td>
        Free text
      </td>
    </tr>

    <tr>
      <td>
        `component`
      </td>

      <td>
        Debian
      </td>

      <td>
        Free text
      </td>
    </tr>

    <tr>
      <td>
        `digest`
      </td>

      <td>
        Docker
      </td>

      <td>
        Free text
      </td>
    </tr>

    <tr>
      <td>
        `v1`
      </td>

      <td>
        Docker
      </td>

      <td>
        Free text
      </td>
    </tr>

    <tr>
      <td>
        `appVersion`
      </td>

      <td>
        Helm
      </td>

      <td>
        Free text
      </td>
    </tr>

    <tr>
      <td>
        `groupID`
      </td>

      <td>
        Maven
      </td>

      <td>
        Free text
      </td>
    </tr>

    <tr>
      <td>
        `artifactID`
      </td>

      <td>
        Maven
      </td>

      <td>
        Free text
      </td>
    </tr>

    <tr>
      <td>
        `classifier`
      </td>

      <td>
        Maven
      </td>

      <td>
        Free text
      </td>
    </tr>

    <tr>
      <td>
        `scope`
      </td>

      <td>
        npm
      </td>

      <td>
        Free text
      </td>
    </tr>

    <tr>
      <td>
        `keywords`
      </td>

      <td>
        npm
      </td>

      <td>
        Free text
      </td>
    </tr>

    <tr>
      <td>
        `boxProvider`
      </td>

      <td>
        Vagrant
      </td>

      <td>
        Free text
      </td>
    </tr>

    <tr>
      <td>
        **Artifacts > Archive Entries**
      </td>

      <td>

      </td>

      <td>

      </td>
    </tr>

    <tr>
      <td>
        `path`
      </td>

      <td>

      </td>

      <td>
        Free text
      </td>
    </tr>

    <tr>
      <td>
        `classResourcesOnly`
      </td>

      <td>

      </td>

      <td>
        Indicates whether to search according to class resources only.

        Possible values: true, false

        Default value: false
      </td>
    </tr>

    <tr>
      <td>
        `excludeInnerClasses`
      </td>

      <td>

      </td>

      <td>
        Indicates whether to exclude inner classes are part of the search.

        Possible values: true, false

        Default value: false
      </td>
    </tr>

    <tr>
      <td>
        `checksumSearch`
      </td>

      <td>

      </td>

      <td>
        Indicates whether the search pattern needs to be searched as a checksum

        Possible values: true, false

        Default value: false
      </td>
    </tr>
  </tbody>
</Table>

## Free Text Search

You can search by using one or more words, terms that include wildcard symbols, and Boolean expressions.

**To search using free text**:

* In the search box at the top of the platform UI window, type a string that reflects the name of the item you are searching for. You can use wildcard symbols such as \* (all), and Boolean expressions. Then click **Enter**. The search results are displayed.

## Advanced Search Using Filters

You can narrow down your search results for complex searches by setting filters in the the advanced filtered search. The search contains filters that apply to all the resources, for example, name and data range, and resource-specific filters in your `docker-local` repository that have a specific Docker tag. For example you can search for all the Docker images in your`docker-local`repository that have a specific Docker tag.

**To use advanced search filters**:

1. From the left-hand side of the search box at the top of the platform UI, select a resource type, for example, **Packages**.
2. Click **Advanced Search** ![](https://files.readme.io/0eb2d465f047d09c9aa3fb484714013da22af0aa65e1c5a2e481b8ac4ef4bd57-uuid-b3dfa9cd-77c5-1190-478e-e1ba680d938f.jpg) to the right of the search field. **Advanced Search** options are displayed for that resource type.
3. Configure **Advanced Search** options for the resource type you have selected. Click a resource type to see its options:

   * [Package Search](#package-search)
   * [Artifacts Search](#artifacts-search)
   * [Build Search](#build-search)
   * [Release Bundles Search](#release-bundles-search)
   * [Xray Search](/docs/searching-for-scanned-resources)
   * <Anchor label="Archive Search" target="_blank" href="/administration/docs/cold-storage#search-and-restore-archived-artifacts-or-packages">Archive Search</Anchor>

**Example**

If ​**Packages**​ is chosen from the list to the left of the search field, you can click the Advanced Search button ​​​to display the advanced filtering options for packages. For example, a Type field appears listing package types, from which you can choose ​**Docker**​​, for example. JFrog then adds the `​pkgType:docker`​​ keyword to the search bar to search for a Docker package.

### Package Search

Package Search allows you to search for packages using a number of parameters. For important information that will help you better search for Packages and Artifacts, see [Searching in Artifactory](/docs/understanding-how-to-search-for-artifacts-and-packages).

**To search for packages**:

1. From the left of the search field at the top of the platform UI, select **Packages**.
2. From the right of the search field, click **Advanced Search** ![](https://files.readme.io/0eb2d465f047d09c9aa3fb484714013da22af0aa65e1c5a2e481b8ac4ef4bd57-uuid-b3dfa9cd-77c5-1190-478e-e1ba680d938f.jpg) . Advanced Search options are displayed.

   <Image align="center" border={true} width="50% " src="https://files.readme.io/a4d883cb80a6290854b51d0ec3785a614ce30df1a1f48ffa7065847c897e0eb9-advanced-search_packages-closeup.png" className="border" />
3. Configure **Advanced Search** options using any of the following parameters:
   * **Type**: Select the package from the Type list.
   * **Name**: Enter the package name.
   * **Description**: Search for keywords in the package description for supported packages
   * **Keywords**: Search for keywords in the package metadata, for supported packages. Keywords may be called 'tags' or 'labels' for different packages types.

### Build Search

Build Search allows you to search for builds using a number of parameters.

**To search for builds**:

1. From the left of the search field at the top of the platform UI, select **Builds**.
2. From the right of the search field, click **Advanced Search** ![](https://files.readme.io/0eb2d465f047d09c9aa3fb484714013da22af0aa65e1c5a2e481b8ac4ef4bd57-uuid-b3dfa9cd-77c5-1190-478e-e1ba680d938f.jpg). Advanced Search options are displayed.

   <Image align="center" alt="search_builds (1).png" width="60% " src="https://files.readme.io/d8c303abc51ab95aa6cf42e944666081c15d6dca95a88899c7375f35cc25eb7e-uuid-6e278c46-46c4-2cf3-fe93-14cd74ea518c.png" />
3. Configure **Advanced Search** options using any of the following parameters:
   * **Name**: The build name
   * **Created After/Created Before**: The date range in which the build was deployed

### Artifacts Search

Artifact Search offers a number of search parameters based on the type of artifact you're searching for. Each search type offers a set of input fields corresponding to the search type you selected to help narrow down your search.

<Callout icon="📘" theme="info">
  **Note**

  Browse and search for Artifacts in the dedicated Artifacts search by navigating to **Artifactory > Artifacts**. For more information, see [Search for Artifacts](https://docs.jfrog.com/artifactory/docs/search-for-artifacts).
</Callout>

**To search for artifacts in the platform search**:

1. From the left of the search field at the top of the platform UI, select **Artifacts**.
2. From the right of the search field, click **Advanced Search** ![](https://files.readme.io/0eb2d465f047d09c9aa3fb484714013da22af0aa65e1c5a2e481b8ac4ef4bd57-uuid-b3dfa9cd-77c5-1190-478e-e1ba680d938f.jpg). Advanced Search options are displayed.

   <Image align="center" border={true} width="50% " src="https://files.readme.io/d14135a3c7e70927b5480dfa199474c822021f14e378205c6d8e244a9be90405-advanced-search_artifacts-closeup.png" className="border" />
3. Select a **Type**. Advanced search options vary depending on the type of artifact you are searching for. The following artifact types are available. Click for more information on what is offered in each, then complete the fields as needed:

   * [Quick Search](#quick-search)
   * [Artifact Package Search](#artifact-package-search)
   * [Property Search](#property-search)
   * [Checksum Search](#checksum-search)
   * [Trash Search](#trash-search)
4. Take action on an artifact, if required. Several actions are available based on the resource, by clicking the arrow on the far right, as follows:

   <Image align="center" border={true} width="80% " src="https://files.readme.io/6a41518efaff47ebfe59bfee17b91d38295560edb529e7e7517d2d1cff84b3a7-advanced-search_artifacts-results.png" className="border" />

#### Quick Search

Using Quick Search you can search for artifacts by name and repositories. From the search type dropdown, select **Quick,** enter your search terms, and click **Search**.

**To run a quick search**:

1. From the left of the search field at the top of the JDP window, select **Artifacts**.
2. From the right of the search field, click **Advanced Search** ![](https://files.readme.io/0eb2d465f047d09c9aa3fb484714013da22af0aa65e1c5a2e481b8ac4ef4bd57-uuid-b3dfa9cd-77c5-1190-478e-e1ba680d938f.jpg). **Advanced Search** options are displayed.

   <Image align="center" alt="quick search artifacts.png" width="70% " src="https://files.readme.io/1921246f2063de3f43d996b6649d954f4c786a6ed59cc53774d0b44f87e4f614-uuid-28f6afd1-382c-a965-24b2-6aaa3dc5d136.png" />
3. From the **Type** menu, select **Quick**. Quick search options are displayed.
4. Configure as needed and run your search. You can specify the following parameters for your search:

| Parameter    | Description                                                                        |
| ------------ | ---------------------------------------------------------------------------------- |
| Name         | Type the name of the artifact. You can use ? and \* as wildcards                   |
| Repositories | Select specific repositories from the Repositories list to narrow down your search |

#### Package Type Search

Package search enables you to run a search based on a specific packaging type. For each type, you can specify search parameters based on the relevant metadata for the selected package type. For example, **Helm** search is suitable for searching through Helm Chart repositories.

<Callout icon="📘" theme="info">
  **Under the hood**

  Package search is based on standard properties that Artifactory attaches to packages according to their type. For example, when searching for NuGet packages, Artifactory is actually matching the search terms to the values for the `nuget.id` and `nuget.version` properties that should be attached to every NuGet package.
</Callout>

<Callout icon="📘" theme="info">
  **Limitation**

  Package search does not currently work on remote repository caches for RubyGems, Debian, and PHP Composer repositories.
</Callout>

**To search artifacts by package type**:

The following table displays the parameters you may use for each package type:

1. From the left of the search field at the top of the JDP window, select **Artifacts**.
2. From the right of the search field, click **Advanced Search** ![](https://files.readme.io/0eb2d465f047d09c9aa3fb484714013da22af0aa65e1c5a2e481b8ac4ef4bd57-uuid-b3dfa9cd-77c5-1190-478e-e1ba680d938f.jpg). **Advanced Search** options are displayed.

   <Image align="center" alt="search_artifacts_by_packages (1).png" width="70% " src="https://files.readme.io/3a375a48096fbfa81bd87692c0f9a648be578319853cf5efaf2249891097ed1a-uuid-aa9ecbbe-9d9a-38ab-ae9c-7077d0bee0bb.png" />
3. From the **Type** menu, select **Package**. Package options are displayed.
4. Select a package type to base the search on.

All these search fields support the `?` and `*` wildcard characters.

<Callout icon="✅" theme="okay">
  **Package search as an AQL query**

  For most package formats, package search is implemented as an AQL query. After searching, click the `AQL Query` button to view the AQL query used in the search. You may also click the `Copy` icon in the AQL code snippet to copy the query to your clipboard.
</Callout>

<Callout icon="📘" theme="info">
  **Limit search to specific repositories**

  When limiting search to specific repositories, you can select repositories with the corresponding package type. Package search depends on those repositories having the correct layout. Searching through repositories with the wrong layout will have unpredictable and unreliable results.
</Callout>

The example below shows the results of searching for any Docker image with `latest` in its name:

<Image align="center" alt="search type package latest (1).png" width="60% " src="https://files.readme.io/9b88c0cb1523b51aaeba20d631b4b84bcaf61bb40b89f296c97327241c60e4d7-uuid-5a7bc218-4269-6021-61fa-755522af5d22.png" />

#### Property Search

<Callout icon="📘" theme="info">
  **Note**

  The Property Search requires an Artifactory Pro license and above.
</Callout>

You can search for artifacts or folders based on [properties](/docs/jfrog-properties) assigned to them, whether they are standard properties assigned by Artifactory, or custom properties which you can freely assign yourself.

**To run a property search**:

1. From the left of the search field at the top of the JDP window, select **Artifacts**.
2. From the right of the search field, click **Advanced Search** ![](https://files.readme.io/0eb2d465f047d09c9aa3fb484714013da22af0aa65e1c5a2e481b8ac4ef4bd57-uuid-b3dfa9cd-77c5-1190-478e-e1ba680d938f.jpg). **Advanced Search** options are displayed.

   <Image align="center" alt="property_search (1).png" width="70% " src="https://files.readme.io/134dd7c985e1faa591b5550882ea3224d7dad9a04f61b775c03cb6a4642745a2-uuid-2e4ddde5-4bcd-934f-758f-7c77f176fd7a.png" />
3. From the **Type** menu, select **Property**. Property search options are displayed.
4. Click **Add Property** and in the **Key** field, type the name of the property to search for, or select one from the list provided.
5. In the **Value** field, set the value you are searching for in the specified property.
6. Add more properties to the search use the **Add Property** as required, then click **Search**. The search is run. You can repeat this process to specify any number of properties and values for your search.

<Callout icon="✅" theme="okay">
  **Wildcards can be used in the Property Value field**

  You can use the `?` or `*` wildcards in the **Value** field.
</Callout>

**Combining Properties and Values**

Properties can be combined using the `AND` operator.

Different values assigned to a specific property can also combined using the `AND` operator.

This means that only artifacts that meet all the search criteria specified will be found.

The following example shows a search for artifacts that have a `build.number` property with a value of 2.

<Image align="center" alt="property_search_example (1).png" width="70% " src="https://files.readme.io/21bc0da08a631c8c7a7014195ce6e1e37c41796823e15ac0d9764b814129464e-uuid-a985f100-7246-2f1f-ef2a-015c2fe45349.png" />

#### Checksum Search

You can search for artifacts based on their MD5, SHA1 or SHA2 checksum value. This can be especially useful if you want to identify an artifact whose name has been changed.

**To run a checksum search**:

1. From the left of the search field at the top of the JDP window, select **Artifacts**.
2. From the right of the search field, click **Advanced Search** ![](https://files.readme.io/0eb2d465f047d09c9aa3fb484714013da22af0aa65e1c5a2e481b8ac4ef4bd57-uuid-b3dfa9cd-77c5-1190-478e-e1ba680d938f.jpg). **Advanced Search** options are displayed.
3. From the **Type** menu, select **Checksum**. Checksum search options are displayed.
4. Copy and paste a **checksum**, then select a **repository** to search in and click **Search**. Wildcard characters are not supported in Checksum Search, so the term entered in the search field must be a valid MD5 or SHA1 value.

The following example shows a search for an artifact using its SHA1 checksum.

<Image align="center" alt="checksum filter (1).png" width="60% " src="https://files.readme.io/341e4e11c289266bf4bc0b2bf803135ae1fb596b45e563a5414f163c05524a8c-uuid-e55fce0d-1856-89b3-b490-e27067af568d.png" />

#### Trash Search

Trash Search is a search type that can be selected as part Searching Artifacts.

**To run a Trash search**:

1. From the left of the search field at the top of the JDP window, select **Artifacts**.
2. From the right of the search field, click **Advanced Search** ![](https://files.readme.io/0eb2d465f047d09c9aa3fb484714013da22af0aa65e1c5a2e481b8ac4ef4bd57-uuid-b3dfa9cd-77c5-1190-478e-e1ba680d938f.jpg). **Advanced Search** options are displayed.

   <Image align="center" alt="trash npm (1).png" width="60% " src="https://files.readme.io/bb6def650dbf626fbe1ff8defedf396303c203bf8315cfaea5ae2018fea69910-uuid-af66bab8-77da-85ab-0c02-2de55a6b78bf.png" />
3. From the **Type** menu, select **Trash**. The Trash search options are displayed.
4. Enter the artifact's name in the Query field, or select Checksum Search and type the artifact's checksum.
5. Click **Search**. The search results are displayed.

### Release Bundles Search

<Callout icon="📘" theme="info">
  **Note**

  The Release Bundles Search requires JFrog Distribution be installed with an Enterprise+ license.
</Callout>

The Release Bundles search enables you to search for distributable and received Release Bundles within a specified time page.

**To search for a release bundle**:

1. From the left of the search field at the top of the platform UI, select **Release Bundles**.
2. From the right of the search field, click **Advanced Search** ![](https://files.readme.io/0eb2d465f047d09c9aa3fb484714013da22af0aa65e1c5a2e481b8ac4ef4bd57-uuid-b3dfa9cd-77c5-1190-478e-e1ba680d938f.jpg). Advanced Search options are displayed.

   <Image align="center" alt="search_release_bundles (1).png" width="60% " src="https://files.readme.io/7fb9d28e89f54f21b49b75a104d3e03ef448067e26f162da5bec69ebbdc0e8b4-uuid-288f570e-0600-dd17-654e-bfe36e6e13ef.png" />
3. Configure **Advanced Search** options using any of the below parameters.

   * **Name**: Type the name of the Release Bundle.
   * **Created After**: Pick a date after which the Release Bundle was created (start date).
   * **Created Before**: Pick a date before which the Release Bundle was created (end date).
4. Click **Search**. The search is run and results are displayed below.